Loading Profile...
What is the current rate limit for Twitter?
I'm trying to access Twitter using Twhirl or Tweetdeck on my computer, and using Twittelator on my iPhone but am getting the rate exceeded message and I can't get any of them to download my friends Tweets. Oddly enough TwitterFox is okay, and Twittelator has now started receiving again.
What is the current limit?
What is the current limit?
I’m confused
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?According to http://status.twitter.com , the current API rate is limited to 100 requests per hour. Move your mouse over the (currently green) API bar to see this.
If you're using more than one 3rd.-party Twitter application at the same time, all of them will eat into your limit. Some applications use up more than one API call for each refresh.
As I recall it from the days when the limit was 20 API requests per hour, Twitbin gave me the Rate exceeded message after about 50 minutes. New tweets started coming in 10 minutes later; after a further 50 minutes, I'd get the message again, followed by another 10 minutes' pause until the next hourly allocation began.
I’m happy we're no longer limited to 20 API requests per hour!
-
Inappropriate?You can also check the current utilization of your account's API limit by visiting this URL: http://twitter.com/account/rate_limit...
It should return something like this on your browser:
< hash>
< hourly-limit type="integer">100< /hourly-limit>
< remaining-hits type="integer">97< /remaining-hits>
< reset-time-in-seconds type="integer">1222952746< /reset-time-in-seconds>
< reset-time type="datetime">2008-10-02T13:05:46+00:00< /reset-time>
< /hash>
Hourly-limit indicates the current API limit per user per hour
Remaining-hits indicates the number of requests you can still make in the current hour
Reset-time indicates when the next hour begins (time expressed in GMT).
Thankfully, requests for the current rate_limit_status do not count against the rate limit (at least for now).
I’m in a good mood
1 person says
this answers the question
-
Inappropriate?Thanks for posting that, mdy! 8-)
FWIW: In Google Chrome I receive that information as just a single line and in a different order, like this:
99 2008-10-02T12:56:54+00:00 100 1222952214
I’m happy I now know where to check.
3 Comments Add a comment
This answers the question
-
Yes, I see the same behavior in Chrome. Not sure why. I guess they handle the xml differently. I had to go to Firefox to get the text that I used in the reply above. -
All WebKit-based browsers just display XML as plain text, with all of the tags (like < anything >) hidden. Also, Twitter seems to send the rate_limit_status XML in a random order, so you can't just say the 3rd part is the allow limit. Simply view the source, and all should be good.
-
"Simply view the source" is a great tip. That didn't even occur to me! haha! Thanks, Chris!
