Thank you for your quick reply. I found out I was indeed rate limited, allthough i cant imagine having done 150 requests testing my app only once.
Thanks anyway. On 15 feb, 23:41, Abraham Williams <4bra...@gmail.com> wrote: > You can check if you are getting rate limited with this > method:http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0ra... > > If you are using OAuth onhttp://api.twitter.comthen you should be getting > 350 (last I heard) hits per hour. Otherwise you will be limited to 150/h. > > Abraham > > > > > > On Mon, Feb 15, 2010 at 07:32, b...@mindbus.nl <b...@mindbus.nl> wrote: > > Hi, > > > I was creating a simple application which requests statuses of a > > certain list within my Twitter account using the following command: > >http://api.twitter.com/1/id/lists/list-id/statuses.xml. > > > For some reason, after doing some requests, i get a HTTP 400 Bad > > Request. > > I have read that a client may only do 500 requests per hour, but i > > dont believe that i have done that many requests by simply testing my > > application. > > After some time all is well and i receive the expected result. > > > Has someone else encountered this problem? > > > I have already sent a request to whitelist my IP, but i want to make > > sure that not else is causing this problem. > > > Thanks in advance. > > -- > Abraham Williams | Community Advocate |http://abrah.am > Project | Out Loud |http://outloud.labs.poseurtech.com > This email is: [ ] shareable [x] ask first [ ] private. > Sent from Seattle, WA, United States- Tekst uit oorspronkelijk bericht niet > weergeven - > > - Tekst uit oorspronkelijk bericht weergeven -