Correction: Search API uses a higher limit then the other endpoints. It is not documented in the API, so I'm not sure what the limit would be.
http://apiwiki.twitter.com/Rate-limiting On Wed, May 13, 2009 at 12:23 PM, Josh Roesslein <[email protected]>wrote: > The hits are charged to the user's account if you authenticate. If you > don't provide > authentication credentials then the hits are charged to your IP address. > You are limited to 100 requests per a hour. This limit applies to all API > endpoints that are rate limited. > So calling a search every 15s will cause you to run out of requests pretty > quick. > > Hope that clears things up for you. > > > On Wed, May 13, 2009 at 9:59 AM, szimek <[email protected]> wrote: > >> >> Hi, >> >> I'm using "Sign in with twitter" functionality - since account/ >> verify_credentials request is rate limited, how can I otherwise get >> info about authenticated user? >> >> How exactly requests are limited? I.e. I got 100 users logged in in my >> web app and they all display page with their friends/followers list. >> Will these requests be counted for these users' accounts or IP of my >> server? >> >> What's the limit for search requests? We're using jsonp for fetching >> search results, so at least in this case the limit is for client's IP. >> Is it ok to make search request i.e. every 15s? >> >> Thanks in advance >> > >
