This snapshot, taken on
17/05/2010
, shows web content acquired for preservation by The National Archives. External links, forms and search may not work in archived websites and contact details are likely to be out of date.
 
 
The UK Government Web Archive does not use cookies but some may be left in your browser from archived websites.

Basic Auth Deprecation on June 30, 2010

Attention! June 30, 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 »

Don't fret! @twitterapi is here to help! Feel free to reach out to us directly, or via our Twitter Development Talk group.

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.

Choose your authorization path.

Integrate Twitter seamlessly into your site with just a few lines of Javascript. Learn more