The Rebirth of Twitter’s API

twitter-apiRemember last year when Twitter caused a big controversy by announcing that their new API  strategy would include a 100,000 user limit? Well, today is the day that Twitter API v1.0 is finally being laid to rest. While it was the user limit that made big news back in the fall of 2012, Twitter is also making some  bold statements with some of the changes they’ve made in this version, such as dropping support for everything except JSON and requiring applications to authenticate all of their requests with OAuth 1.0a.

The Slideshare presentation below takes a look back at some other popular APIs that have met their demise, gives an overview of what’s new with Twitter’s API v1.1, and provides information on how to protect yourself (and your app) from being negatively impacted by these kinds of changes in the future.

See also:

Comments

  1. Terence says:

    As a developer, I personally think Twitter API is worst out of ALL the other APIs. It plays on it’s own (it’s own rules, i.e. not returning emails for users authenticated, which makes it pointless to use Twitter Connect), still implements OAuth 1.0a, while everyone else is moving on to OAuth 2.0. Their developer advocate either sucks really bad, or never developed using their own API.

  2. Jim Osterman says:

    Tracking the API universe this year has been like trying to predict which way the wind is going to be blowing five minutes from now. The good news about that is that it offers opportunity for those not afraid to innovate and chases away those who want to play it safe.

Speak Your Mind

*