[twitter-dev] Re: Confused about rate limits

2011-04-12 Thread impeto
You actually have to put the "1" before "account": http://api.twitter.com/1/{end point}.json I just now realized that the CodeIgniter library that I use does not add the version number. I guess I'll have to send the developer a note on that. Hey! It works fine now. Thank you. I would have never th

[twitter-dev] Re: Confused about rate limits

2011-04-12 Thread impeto
well, i did the first time and it didn't work (in the sense that I got a 404 or 401 error -- don't remember which). then i tried it my way and it worked fine. the api doc says that's the right way too: http://dev.twitter.com/doc/get/account/rate_limit_status Alin On Apr 12, 12:27 pm, hax0rsteve

Re: [twitter-dev] Re: Confused about rate limits

2011-04-12 Thread hax0rsteve
Sorry, my bad, that should indeed be http://api.twitter.com/1/... On 12 Apr 2011, at 17:17, impeto wrote: > You actually have to put the "1" before "account": > http://api.twitter.com/1/{end > point}.json I just now realized that the CodeIgniter library that I > use does not add the version n

[twitter-dev] Re: Confused about rate limits

2011-04-12 Thread impeto
use http://api.twitter.com/1/{resource endpoint}.{format} you have to use the version number to get the right results. It works on my app correctly now. If you happen to use the CodeIgniter Twitter library from here https://github.com/elliothaughin/codeigniter-twitter you have to go in tweet.php @

Re: [twitter-dev] Re: Confused about rate limits

2011-04-12 Thread hax0rsteve
Use http://api.twitter.com/account/1/rate_limit_status.json On 12 Apr 2011, at 17:15, Digga wrote: > This is something I am experiencing as well. There is clearly 150 that > is awarded to the accounts per hour. I signed out and signed in, ad > every time there is 150 requests, not 350. > > I

[twitter-dev] Re: Confused about rate limits

2011-04-12 Thread Digga
This is something I am experiencing as well. There is clearly 150 that is awarded to the accounts per hour. I signed out and signed in, ad every time there is 150 requests, not 350. Is there suppose to be 350 or 150 coming from this call? http://twitter.com/account/rate_limit_status.json because

Re: [twitter-dev] Re: Confused about rate limits

2011-04-12 Thread hax0rsteve
You appear to be using the wrong URLs. Specify a version number and this will go away. Rather than "http://api.twitter.com/account/rate_limit_status.json"; use "http://api.twitter.com/account/1/rate_limit_status.json"; On 12 Apr 2011, at 16:06, impeto wrote: > :) Ok, "authenticated" mea

Re: [twitter-dev] Re: Confused about rate limits

2011-04-12 Thread Arnaud Meunier
Hey Alin, The sentence you used confused me, sorry. Now I guess you were talking about the "account/verify_credentials" endpoint :) Question for you: what is your X-RateLimit-Limit header value (for both account/verify_credentials and other endpoints you're using that require authentication)? Ar

[twitter-dev] Re: Confused about rate limits

2011-04-12 Thread impeto
:) Ok, "authenticated" means what it means in the context of the API calls. I am a developer, I make the difference. Perhaps I wasn't too clear: first I used cURL to call "http://api.twitter.com/account/ rate_limit_status.json" anonymously, no oauth tokens, nothing, and I got 150. Then I used a Cod