August 16, 2010
The @twitterapi team will be shutting off basic authentication on the Twitter API. All applications, by this date, need to switch to using OAuth. Read more »
The switch to OAuth is a good thing! You, as the application developer,
don't have the burden of keeping potentially damaging credentials for your users (especially considering that a lot of people use the same password for multiple services);
don't have to worry about the user changing their password — a user can change his or her password and the OAuth "connection" to your app will still work;
don't have to worry about other applications masquerading as your application as only your application can set the byline with your application name;
will eventually have access to more trusted APIs from Twitter that will only be available to "trusted" OAuth-enabled applications; and
will be contributing to the web of trust between users, service providers, and applications.
Twitter exposes its data via an Application Programming Interface (API). These documents are the official reference for that functionality.
Getting started with the Twitter API is easy. Jump right into the resource documentation or read some of the fine literature below.
Note: As we prepare this new developer portal, you might find some pieces of documentation missing. Consider looking on the Twitter API Wiki if you can't find what you're looking for while we are in transition.