Twitter web limits vs API app limits

August 20, 2009
By

Do you tweet from the web or from an application like tweetdeck or seesmic? Did you know the API limits are separate from Per Hour Tweet & Daily Follow limits as are the API calls limits you see in tweetdeck, “Remaining API for account XYZ 150/150 Resets 20 minutes”tweets

Tweetdeck users might have noticed their hourly API call limit has been increased from 100 to 150 per hour as of July 2009.

The Twitter API is made up of two parts. There is the REST API and Search API. The Twitter REST API methods allow developers to access core Twitter data. This includes update timelines, status data, and user information. The Search API methods give developers methods to interact with Twitter Search and trends data.

Methods to retrieve data from the Twitter API require a GET request.  Methods that submit, change, or destroy data require a POST.  A DELETE request is also accepted for methods that destroy data. API Methods that require a particular HTTP method will return an error if you do not make your request with the correct method. HTTP Response Codes are meaningful.

So what can you do to avoid the “rate limit exceeded” message and what can you do if you get it? Unfortunately not very much. This is a Twitter enforced limitation rather than a TweetDeck one but I would suggest the following to reduce the risk:

  • Operate with one twitter application at a time. Make sure the other apps are closed
  • Don’t over use the refresh button – that burns 3 calls per click (All Tweets, Replies & DMs)
  • Lower the total % in the settings window, twitter API tab to around 50-60% – you’ll get less updates but you’ll use less API calls too.
  • If you exceed the rate limit, check your reset time shown in the top right corner of TweetDeck. You can still post messages, butt won’t see any @ or DM responses

Tags: , ,

Post comment as twitter logo facebook logo
Sort: Newest | Oldest