Showing posts with label Twitter API. Show all posts
Showing posts with label Twitter API. Show all posts

Friday 14 June 2013

API v1 Retirement is Complete - Use API v1.1 instead

Twitter has recently translated it's API v1 and fully transitioning it to API v1.1

The Twitter platform is constantly evolving and there is frequent change. If you have an integration that's no longer working, be sure and review the developer blog,platform calendar, recent tweets by the @twitterapi account, the API status dashboard, recently updated documentation and Twitter's status blog athttp://status.twitter.com

API v1 is currently set to retire on June 11, 2013. After retirement (and during the blackout tests leading up to retirement), you can expect the following: 

  • Authenticated & unauthenticated requests to api.twitter.com/1/* will receive HTTP 410 Gone. Use API v1.1 instead.
  • Requests to search.twitter.com/search.* will receive HTTP 410 Gone. Use GET search/tweets instead.
  • Requests to api.twitter.com/1/statuses/oembed.* will continue to be serviced. However, we strongly encourage developers to tolerate HTTP redirects if continuing to use this endpoint.
  • Basic Auth will be disabled on stream.twitter.com/* for all users in non-elevated Streaming API roles. Such requests will receive a HTTP 401Unauthorized. We strongly recommend all Streaming API users, including those in elevated roles, to migrate to OAuth 1.0A now.
  • Requests to Streaming API paths with versions other than "1.1" (such as stream.twitter.com/1/statuses/filter.json) are deprecated — but will not be retired at this phase. We strongly recommend you move to 1.1-era Streaming API paths now.
  • API v1.1 is documented as SSL-only. Make sure you're using SSL and verifying peers — see this guide for more information. Non-SSL requests will eventually be rejected.
  • Legacy widgets (AKA "Goodie" or "Join the Conversation" widgets) will no longer populate with Tweets.
  • JSON is API v1.1's only output format. XML, RSS, and ATOM response formats will be retired along with API v1.