Update: Twitter will permanently depreciate API V1 (that this post refers to) on May 7th. Please check out my Twitter OAuth tutorial for how to get your feeds fully authenticated as required by API V1.1.
At some-point on the 12th October 2012, I noticed a number of websites with integrated JavaScript .json Twitter feeds had stopped working. The error message that appeared whenever I tried to visit the json Twitter URL direct was: {“errors”:[{“message”:”Sorry, that page does not exist”,”code”:34}]}
It looks like Twitter have recently updated the URLs or ‘endpoints’ for their feed links, so if your twitter stream path looks something like:
http://twitter.com/status/user_timeline/user_name.json, this has been depreciated, and should now be:
http://api.twitter.com/1/statuses/user_timeline/user_name.json
Hope that helps some of you, it didn’t take too long to fix the problem (and update around 10 sites) once I knew what the issue was
I will also be following @twitterapi to make sure I don’t miss out on any future updates!
thanks for the info, it’s help my blog twitter feed keep running 🙂
Thanks a million boss you saved my nose in just few minutes…
thank you so much for this….fixed my issue right up!