Last month, Twitter announced that some big changes were coming to its API. So developers and the Twitter ecosystem knew this was coming. But, today, the company officially unveiled the newest version of its API, v1.1, and updated its “Developer Rules of the Road” and display requirements.
One of the more notable changes we’ve seen so far, brought to our attention by Steve Streza’s tweet, is that developers will have until March 5, 2013 to switch over to the new version of the API. After that, v1.0 will be “kaput” — to use the technical term. Twitter writes that it wants to provide developers with ample time (a 6-month window) before turning off v1.0., at which point endpoints “will no longer be available.” More about the deprecation of v1.0 in Twitter’s API Overview here.
Timelines aside, whether or not developers will be happy about transitioning to the new API is another question. Anthony has already laid out how life will get a bit harder for developers of traditional Twitter client apps under the new API, among other ways in which Twitter is tightening the screws on its ecosystem.
For starters, apps that are pre-installed on mobile devices need to be approved by the company first. But perhaps the issue that’s created the most buzz among developers is the 100,000-token limit imposed by Twitter on third-party apps, meaning that if an app exceeds 100K user tokens (or some-100K users), it will have to work directly with Twitter. As Klint subsequently pointed out, the rule was essentially instituted to “supervise” the development (and developers) of third-party apps.
In its blog post today, Twitter specifically addressed this issue, offering a point of clarification, saying, “the 100,000 user token limit applies only to the small set of clients replicating the core Twitter experience. It does not apply to the majority of other applications in the broader ecosystem.”
Updating
