If you didn’t participate in Twitter’s blackout test last month, please get out your calendar and be sure to take part in this one – or you may find yourself on our API death watch series, or worse – the Twit list.
You’ve been warned.
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.
And that’s pretty big of them, considering the old API was supposed to go bye-bye at the end of last month. And when API v1 retires, “all authenticated and unauthenticated requests to API v1 will return a HTTP 410 Gone status. Older widgets will receive the same response. This status code signifies that all API v1-era resources are gone and not coming back.”
So beyond making you face the harsh reality of your app’s impending doom, the blackout tests are meant to help you better understand the impact the retirement will have on your applications and users – and make some changes (if you can) while you still can.
If you haven’t been keeping track of everything you should have during this forced migration, check out this handy list of what to expect:
- 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 asstream.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 guidefor 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.
Did you participate in the last blackout test? Maybe your experience won’t be all doom and gloom. At least one developer is actually pleased with API 1.1. Where do you stand?
(Image from Shutterstock)
- Two More Twitter API Casualties: TweetChat and TweetGrid
- Twitter Settles Suit With TweetAdder, Allowing Tool Once Labeled As Spam Continued Access
- Twitter Ads App Throws Its Neck On Chopping Block
- Breaking! PeopleBrowsr Reaches Firehose Settlement With Twitter