本文介绍了Twitter状态API突然返回错误"34"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我有一个脚本可以从我的Feed中获取前3条推文.一切正常,但现在它在JSON中返回以下错误:
I have a script that gets the top 3 tweets from my feed. This was working just fine but now it is returning the following error in the JSON:
{"errors":[{"message":"Sorry, that page does not exist","code":34}]}
Twitter将其描述为经典的404 not found错误,但在Twitter网站上我看不到API状态有任何中断.
Twitter describes this as a classic 404 not found error, but I do not see any disruption from the API status' on the Twitter website.
我们现在获取推文的方式有所改变吗?
Has something changed in the way we now fetch Tweets?
我的代码:
$.getJSON('http://twitter.com/statuses/user_timeline.json?screen_name=' + user + '&count=3&include_rts=true&callback=?', function(data) { });
谢谢.
推荐答案
您使用了错误的链接, https://api.twitter.com/1/statuses/user_timeline/jbrooksuk.json
You're using the wrong link, https://api.twitter.com/1/statuses/user_timeline/jbrooksuk.json
尝试一下:
$.getJSON('http://api.twitter.com/1/statuses/user_timeline/' + user + '.json?count=3&include_rts=true&callback=?', function(data) { });
这篇关于Twitter状态API突然返回错误"34"的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!