Hi Raffi, Correct.
Although per my description below, I still don't see how I would be doing 20,000 calls (or even 150) that quickly. Thanks, Roy On Mar 8, 2:01 pm, Raffi Krikorian <ra...@twitter.com> wrote: > hi! > > are you making calls to api.twitter.com's rate_limit_status? if so, there > is a bug in it that we're addressing. > > > > On Mon, Mar 8, 2010 at 10:50 AM, Roy Rodenstein <roy...@gmail.com> wrote: > > Hi all, I'm new to Twitter API dev, working on a mashup with LinkedIn > > to find your LI network on Twitter. > > > I am only doing a couple of Twitter calls: > > - friends/ids, one per app run > > - user search w/limit of 5 results, about 20 per app run (tho this > > will rise when I'm done testing) > > > So pretty limited API calls right now. Also, I got my @how2startup > > account whitelisted (don't have a static IP yet so can't get IP > > whitelisted I assume), and as you can see below from output of > > rate_limit_status run from my server, I have plenty of API calls left. > > And yet I am still getting Rate Limit Exceeded error. > > > I must be missing something really obvious, or really tricky. Is there > > some other IP (the local browser?) that is getting rate limited? > > Thanks for any tips! Best, Roy > > > IP Address Rate Limit (Unauthenticated call to rate_limit_status) > > <hash> > > <reset-time type="datetime">2010-03-08T09:27:04+00:00</reset-time> > > <remaining-hits type="integer">140</remaining-hits> > > <hourly-limit type="integer">150</hourly-limit> > > <reset-time-in-seconds type="integer">1268040424</reset-time-in- > > seconds> > > </hash> > > > how2startup Address Rate Limit (Authenticated call to > > rate_limit_status) > > <hash> > > <remaining-hits type="integer">19713</remaining-hits> > > <reset-time type="datetime">2010-03-08T10:05:25+00:00</reset-time> > > <hourly-limit type="integer">20000</hourly-limit> > > <reset-time-in-seconds type="integer">1268042725</reset-time-in- > > seconds> > > </hash> > > -- > Raffi Krikorian > Twitter Platform Teamhttp://twitter.com/raffi