JQuery + JSON Request stopped returning results.

mina_asad
@mina_asad Mina Asad

I have been using the following code for some time now and it's been working until the past week or so.

https://twitter.com/statuses/user_timeline.json?screen_name=mina_asad&count=5&callback=?

I get the following message in return:

({"errors":[{"message":"Sorry, that page does not exist","code":34}]});

Is it because the tweets have increased? What am I missing?

51 weeks 5 days ago

Replies

episod
@episod Taylor Singletary

This is a common issue when using outdated unversioned URLs that have now been retired. See this FAQ for more info:

Why am I getting a HTTP 404 for my timeline feed?

If you're requesting a timeline URL that used to work but now does not, you are likely using an outdated URL that has been retired. In March of 2012 we announced that "unversioned endpoints," GET statuses/public_timeline, and the v1 REST ATOM response format were deprecated and would eventually cease functioning. In early October 2012, we turned off these endpoints.

You can identify unversioned endpoints by examining their URL: http://twitter.com/statuses/user_timeline/twitterapi.rss is missing both the API version and the "api" subdomain. The correct URL for the same request would be https://api.twitter.com/1/statuses/user_timeline.rss?screen_name=twitterapi

Please note that there is no support for the RSS response format in API v1.1. Properly versioned API v1 URLs will cease functioning in March 2013.

For help dealing with the Spring 2012 deprecations, see Following up on API housekeeping.

51 weeks 3 days ago