Like Techgeist? Donate.
Need to Contact Us? Read This. Also, find out more about us on the About page.
Advertisement
Advertisement

Twitter Raises API Limits?

By Dan Monzelowsky on July 1, 2009

As I always do, the first thing I did when I got home this evening was to open TweetDeck. What did I see waiting for me?

 

API

Instead of the usual 100 API calls per hour, TweetDeck says that I now have a maximum of 150.

Is this something permanent? I really hope that it is, because that would take us one step closer to real time in our much beloved third party Twitter applications. I, however, was willing to pay for such an increase, to help shoulder the burden of the hardware costs.

Please, Twitter, give me more API calls. Open the fire hose, and I will gladly open my wallet to help you in return.

Share
You can comment either manually filling in your personal information, or you can use your Facebook Account to fill in the information for you. Just click the button below to sign into Facebook.
Have Nothing To Say? Share this article with your friends using one of our share buttons above.

Leave a Comment.

Comments

  1. [...] suggest a rate limit increase across the board, although that’s yet to be confirmed. The blog SocialGeist also spotted the change, and sent us the [...]

  2. [...] suggest a rate limit increase across the board, although that’s yet to be confirmed. The blog SocialGeist also spotted the change, and sent us the [...]

  3. This is pretty nice. That said, the API wiki still says we get 100 an hour. Hopefully we won’t get knocked back to 100. http://apiwiki.twitter.com/Rate-limiting

  4. [...] suggest a rate limit increase across the board, although that’s yet to be confirmed. The blog SocialGeist also spotted the change, and sent us the [...]

  5. [...] This post was Twitted by Sampad [...]

  6. [...] This post was Twitted by debsuvra [...]

  7. [...] suggest a rate limit increase across the board, although that’s yet to be confirmed. The blog SocialGeist also spotted the change, and sent us the [...]

  8. [...] suggest a rate limit increase across the board, although that’s yet to be confirmed. The blog SocialGeist also spotted the change, and sent us the [...]

  9. [...] suggest a rate limit increase across the board, although that’s yet to be confirmed. The blog SocialGeist also spotted the change, and sent us the [...]

  10. [...] suggest a rate limit increase across the board, although that’s yet to be confirmed. The blog SocialGeist also spotted the change, and sent us the [...]

  11. [...] suggest a rate limit increase across the board, although that’s yet to be confirmed. The blog SocialGeist also spotted the change, and sent us the [...]

  12. The official Twitter API wiki has been updated by “Doug Williams”. It now says that we get 150 API calls/hr.
    “The default rate limit for calls to the REST API is 150 requests per hour.” (emphasis added by me)

    It’s funny, though. As of the time I’m writing this comment, the “Search API Rate Limiting” section still says:
    “Note that the Search API is not limited by the same 100 requests per hour limit as the REST API.” (emphasis added by me)

    It looks like someone was in such a hurry to make the update that they didn’t remember to fix all instances of the old API information.

  13. [...] suggest a rate limit increase across the board, although that’s yet to be confirmed. The blog SocialGeist also spotted the change, and sent us the [...]

  14. [...] suggest a rate limit increase across the board, although that’s yet to be confirmed. The blog SocialGeist also spotted the change, and sent us the [...]

  15. [...] suggest a rate limit increase across the board, although that’s yet to be confirmed. The blog SocialGeist also spotted the change, and sent us the [...]

  16. [...] suggest a rate limit increase across the board, although that’s yet to be confirmed. The blog SocialGeist also spotted the change, and sent us the [...]

Leave a Reply