I'm running those queries in a unit test library and they are next to
other methods that succeed. I use the same authentication for all of
them taken from an XML file and the other methods work. Some times
when I wait a few minutes, those methods that I listed as failing work
as well, but most of the time they report they exceed the rate limit
and the methods after them in the tests pass.

On Jan 22, 2:23 am, Alex Payne <[email protected]> wrote:
> Is it possible that you're attempting to log into Twitter with bad
> credentials? When go back to the Twitter web site are prompted to
> solve a CAPTCHA or told that your account is temporarily locked?
>
>
>
> On Wed, Jan 21, 2009 at 17:58, Dimebrain <[email protected]> wrote:
>
> > Currently, when I attempt the following API calls I receive the "rate
> > limit exceeded" error:
>
> >http://twitter.com/statuses/friends.xml
> >http://twitter.com/statuses/followers/someone.xml
> >http://twitter.com/friendships/exists.xml?user_a=me&user_b=someone
>
> > However when I request rate limits I am well within limit (I started
> > making these requests with 100/100). In addition, I I can make other
> > authenticated API calls under my auth credentials and they run fine
> > and dock me correctly against my rate limit. This has been occuring
> > for the last week and a bit.
>
> > No one on this IP address uses Twitter besides me so I can't figure it
> > has to do with my IP address exceeding limits. Does anyone have any
> > ideas? Is it just erratic / erroneous messages returned?
>
> > @Dimebrain
>
> --
> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x

Reply via email to