Deprecations - Spring 2012

Updated on Tue, 2012-05-22 11:05

Updated Schedule

The following deprecations and platform adjustments will occur in the Spring-Summer 2012 season. An updated, clarified and more gradual schedule will be added to this document by the end of May 2012. Please see API Housekeeping for more information.

Summary

  • All non-versioned API endpoints, such as http://twitter.com/statuses/user_timeline, will cease functioning. See the full account of deprecated methods for a complete list.
  • All previously announced-as-deprecated methods will cease accepting requests.
  • GET statuses/public_timeline will also be deprecated. Please use the Streaming API's sample endpoint to obtain a sampling of public tweets.
  • OAuth 1.0A operations must be performed on the api subdomain. Older http://twitter.com/oauth/* paths will cease to be functional.
  • Atom is being removed on all methods currently supporting it as an output format due to disuse. RSS will remain available on these methods.
  • All API methods capable of including Tweet Entities will return them regardless of the value provided by include_entities=true
  • All API methods capable of including retweets will return them regardless of the value provided by include_retweets=true
  • All methods currently supporting cursoring or usage of since_id and max_id will remove support for "classic" pagination through the "page" parameters. See Working with Timelines for more information.

Additional Recommendations

  • Use SSL whenever possible. See Connecting to Twitter API using SSL
  • Be explicit when using a screen_name or user IDs on methods allowing either
  • Use minimal count values; only retrieve the amount of data you need to satisfy a purpose.
  • Use HTTP header-based OAuth instead of query-string OAuth
  • Use JSON responses whenever possible

OAuth changes

All requests for OAuth operations like obtaining request tokens, access tokens, and user authorization must be made through the api.twitter.com domain. Using SSL for all OAuth operations is strongly encouraged.

Deprecated Path Valid Path More Information
//twitter.com/oauth/request_token https://api.twitter.com/oauth/request_token POST oauth/request_token
//twitter.com/oauth/authorize https://api.twitter.com/oauth/authorize GET oauth/authorize
//twitter.com/oauth/authenticate https://api.twitter.com/oauth/authenticate GET oauth/authenticate
//twitter.com/oauth/access_token https://api.twitter.com/oauth/access_token POST oauth/access_token

REST API changes

Completely deprecated resources

These deprecations are effective regardless of whether you're attempting to access them with or without the "api" subdomain or API version "1."

Deprecated Paths Note
GET //twitter.com/statuses/public_timeline.format
GET //api.twitter.com/1/statuses/public_timeline.format
Use The Streaming APIs's statuses/sample.json instead.
GET //twitter.com/statuses/friends_timeline.format
GET //api.twitter.com/1/statuses/friends_timeline.format
Use GET friends/ids & POST users/lookup
GET //twitter.com/statuses/followers/:user.:format Use GET followers/ids & POST users/lookup & GET statuses/user_timeline
GET //twitter.com/statuses/friends/:user.:format Use GET friends/ids & POST users/lookup

Moved Endpoints

Deprecated Paths Valid Path
POST //twitter.com/:user/lists.format POST //api.twitter.com/1/lists/create.format
GET //twitter.com/:user/lists.format GET //api.twitter.com/1/lists.format
GET //twitter.com/:user/lists/memberships.format GET //api.twitter.com/1/lists/memberships.format
GET //twitter.com/:user/lists/subscriptions.format GET //api.twitter.com/1/lists/subscriptions.format
GET //twitter.com/:user/lists/:id.format GET //api.twitter.com/1/lists/show.format
GET //twitter.com/:user/lists/:id/statuses.format GET //api.twitter.com/1/lists/statuses.format
POST //twitter.com/:user/lists/:id.format POST //api.twitter.com/1/lists/update.format
PUT //:user/lists/:id.format POST //api.twitter.com/1/lists/update.format
DELETE //twitter.com/:user/lists/:id.format POST //api.twitter.com/1/lists/destroy.format
POST //twitter.com/:user/:list_id/members.format POST //api.twitter.com/1/lists/members/create.format
POST //twitter.com/:user/:list_id/members.format POST //api.twitter.com/1/lists/members.format
DELETE //twitter.com/:user/:list_id/members.format POST //api.twitter.com/1/lists/members/destroy
GET //twitter.com//:user/:list_id/members/:id.format GET //api.twitter.com/1/lists/show.format
POST //twitter.com/:user/:list_id/subscribers.format POST //api.twitter.com/1/lists/subscribers/create.format
GET //twitter.com/:user/:list_id/subscribers.format GET //api.twitter.com/1/lists/subscribers.format
DELETE //twitter.com/:user/:list_id/subscribers.format POST //api.twitter.com/1/lists/subscribers/destroy.format
GET //twitter.com/:user/:list_id/subscribers/:id.format GET //api.twitter.com/1/lists/subscribers/show.format
GET //twitter.com/statuses/:id.format GET //api.twitter.com/1/statuses/show.format
GET //twitter.com/replies.format GET //api.twitter.com/1/statuses/mentions.format

Unversioned resources requiring use of versioned alternate

All REST API methods must be made using api.twitter.com and the "/1/" version element in a path. Below are some examples of such paths, but the list is not exhaustive.

Deprecated Paths Valid Path Note
//twitter.com/statuses/home_timeline/:id.format
//api.twitter.com/1/statuses/home_timeline.format  
//twitter.com/direct_messages.format //api.twitter.com/1/direct_messages.format  
//twitter.com/search.format
//api.twitter.com/1/search.format
//search.twitter.com/search.format Only available via the unversioned search.twitter.com resource

Search API changes

No changes at this time.

Streaming API changes

No changes at this time.