Twitter Increases Rate Limits by 50%

Adam DuVander
Jul. 02 2009, 01:22PM EDT

Your Twitter mashup may have just got 50% more real-time content. And if you follow many people, you may have already noticed an increase in the flow of information. Why?

That's because in the last 24 hours Twitter quietly increased the limit from 100 to 150 requests per hour (as seen in the update Twitter made to their developer wiki shown below). For a site that has had significant uptime issues in the past, hopefully this is a sign that they can control the firehose.

twitterrate

For a Twitter developer it might mean a little tweak to your code. It is important to keep track of the requests that get sent out, or you'll risk being blacklisted if you attempt to request beyond the limit. You can also get the requests remaining from the Twitter API without being "charged" for a request. High volume applications can request "whitelisting" which, if approved, increases the limit to 20,000 requests per hour.

The update to the rate limit does not effect the search API, which was already "quite a bit higher" than 150 per hour. Twitter does not publish the search limit, but recommends watching for a 503 error, a sign you need to throttle back.

With the increase to the rate limit, perhaps it's time to add your Twitter app to the 200+ Twitter mashups we list, or get more familiar with the Twitter API.

Adam DuVander Hi! I'm Developer Communications Director for SendGrid and former Executive Editor of ProgrammableWeb. I currently serve as a Contributing Editor. If you have API news, or are interested in writing for ProgrammableWeb, please contact editor@programmableweb.com Though I'm a fan of anything API-related, my particular interest is in mapping. I've published a how-to book, Map Scripting 101, to get anyone started making maps on websites. In a not-so-distant past life I wrote for Wired and Webmonkey.

Comments