API changes in the Twitter timeline feed

Getting worked up over the timeline url you had created, that isn’t showing up anymore? Here’s shedding some light.

This recent development has occurred as the url you had wanted has just entered the obsolete list, in other words – it has been taken off, under Twitter’s recent API update. Earlier this year during the month of March, Twitter had declared that “universioned endpoints”, GET statuses/public timeline plus the v1 REST ATOM, had got disapproved and would ultimately stop working.

The move was set to take place in the October 2012, as Twitter was all set to switch off their endpoints.

The Change

You can find out about the universioned endpoints by judging the below mentioned url. It does not have the API version and the “api” subdomain.

https://twitter.com/statuses/user_timeline/twitterapi.rss/

Therefore, the right url for the requirement would be

https://api.twitter.com/1/statuses/user_timeline.rss?screen_name=twitterapi/

Besides, it is also reported that there wouldn’t be any support for the RSS in the API version 1.1.

As the correctly versioned API version 1’s url’s would completely end working by the month of March in 2013.

The API strategy

The idea behind the development is that Twitter is all set to provide an enhanced experience to its users. Let’s figure out the strategy the organization has taken in modifying the API’s as well as in its migration plan, together along with the change in Twitter’s environment.

The version 1.1 of the Twitter API incorporates a few new things, like-

• The authentication would be needed on each API endpoint
• Better Rate Limits
• Enhanced Developer Rules of the Road
• Dev.twitter.com updates
• Fresh Twitter customer policies
• Taking off the version 1.0 of API
• JSON support
• Developer display requirements
• Retweets and default entities
• Feedback and the next steps

All this is a part of the improved strategy of Twitter to make its ecosystem better for one and all.