The Twitter REST API v1 will officially retire on Tuesday, May 7, 2013. (See API v1 Retirement Date Extended to June 11, 2013)
We will hold another blackout test on April 16, 2013 beginning at 23:00 UTC (4:00pm PDT). Depending on the results of that blackout test, we may announce an additional test before the final retirement date.
There’s a lot to keep track of in this migration. Here’s a recap:
- 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 401 Unauthorized. 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 or or ) 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.
If you have remaining questions or are having difficulty migrating to API v1.1, please contribute to this discussion.
Your retirement cruise director,