ok, so I'll optimize my calls to verify_credentials. Would be good if this was documented someplace.
Also, does the same limit exist for other APIs? -fs On Jul 27, 10:39 am, TinBlue <tinb...@gmail.com> wrote: > Twitter in their infinite wisdom decided to implement a limit on the > verify_credentials API call. > > I believe its 15 calls per hour. > > They have since come to their senses and said they will be rolling > back to the previous behavior. However, as yet they still haven't done > it. But personally, I wish they would hurry up! > > On Jul 27, 3:07 am, Francis Shanahan <francisshana...@gmail.com> > wrote: > > > Sorry that's "403 Forbidden" errors I'm gietting. > > > On Jul 26, 10:06 pm, Francis Shanahan <francisshana...@gmail.com> > > wrote: > > > > I realise there are limits on the number of times an application can > > > call into Twitter in a given time period. > > > > In the course of my testing though I tend to fire off a lot of > > > requests, nothing crazy just probably 1 per minute as I'm clicking > > > through my tests. > > > > Sometimes when I'm testing oAuth Login and logging in/out of the > > > application, and going back and forth with the Grant/Deny page I am > > > experiencing 403 Unauthorized errors with the following data in the > > > response > > > > <?xml version="1.0" encoding="UTF-8"?> <hash> <request>/account/ > > > verify_credentials.xml?oauth_consumer_key=[removed] > > > &oauth_nonce=7959883&oauth_signature_method=HMAC- > > > SHA1&oauth_timestamp=1248659818&oauth_token=[removed] > > > &oauth_version=1.0&oauth_signature=TH > > > %2bFof7ErcFdH6XgVgPeou174yI%3d</request> > > > <error>Too many requests in this time period. Try again later.</error> > > > </hash> > > > > This error is just given for my account, other users don't get this > > > error. I can log in from the site with another user without issue. > > > > So given that I'm not making that many requests and can trigger this > > > with just manual clicking, how many are allowed for a given user?
