In March, Twitter announced via its developer blog that its API v1 would officially retire on Tuesday, May 7, 2013.
Well, developers are getting a reprieve – Twitter has delayed the API 1 shutdown until June 11.
Why? Apparently more time is necessary for blackout tests.
This is the second time a delay has been announced; the API was originally supposed to retire in March.
So, what exactly is changing in API 1.1? Michael Sippey, VP of product at Twitter, details the following changes:
- required authentication on every API endpoint
- a new per-endpoint rate-limiting methodology
- changes to Developer Rules of the Road, especially around applications that are traditional Twitter clients
Basically, Twitter wants to set boundaries for its app ecosystem, ensuring that no third-party apps are emulating the Twitter.com experience too closely.
Those clients that do not adhere to the new rules could have their application key revoked. Plus, all third-party apps are going to have to be certified by Twitter before pre-installation.
Luckily, developers have got an extra month to come to terms with the new regulations.
As for users, the impact won’t be visible until the new changes officially take effect, but when they do, it could mean a drastically different experience – for example, if you’re one of the millions of people who use third-party Twitter clients like Tweetbot, Echofon or Twitterific in lieu of Twitter.com or Twitter’s official app. Or if you like to pull in your Twitter feed to Flipboard. Or send interesting links from tweets you read to Instapaper or Pocket to read later.
Guess we’ll see how this all shakes out in just a few weeks.
(Image via Shutterstock)