My experience with rate limiting shows that each authenticated request
is counted against that user's limit on your IP. So, you get 20,000
requests per IP, per user, per hour assuming all your requests are
authenticated. Any unauthenticated requests go towards the 20,000
request limit per IP, per hour.

In my case, all Twitter API calls are authenticated and cached for an
hour. The way my app is set up, under normal usage, no user will use
more than 20,000 Twitter API requests.

Kyle Mulka
Founder, Congo Labs

On Jan 1, 5:43 pm, jojet <> wrote:
> Hi all,
> I was feeling a little clever after working on some Twitter API stuff
> but then thought "oh! I'd better think about Twitters rate
> limiting"...and then that's where my brain started to melt!
> A few bits of info: my web app needs people to authenticate (OAUTH)
> and, from then on, the app analyses their tweets and occasionally
> updates registered user's statuses.
> I've applied for the webserver IP to be white listed which I believe
> gives the app 20,000 requests per hour.
> I've not found the search API to be great when looking for a hashtag
> (sometimes tweets just don't seem to get indexed) so I've gone a stage
> further and am analysing the individual timelines of all my registered
> users via a cron job (the cron job sucks in all of a persons tweets
> greater than the last analysed tweet of the user). This call is made
> via OAUTH/authenticated so I believe such a call depletes the user's
> rate limit quota rather than the IP/authenticated account of the
> webserver quota? Is that correct?
> Thanks for any thoughts here
> Joel

Reply via email to