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)? Arnaud / @rno <http://twitter.com/rno> On Tue, Apr 12, 2011 at 8:06 AM, impeto <[email protected]> wrote: > :) 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 CodeIgniter Twitter library from here > https://github.com/elliothaughin/codeigniter-twitter to authenticate > and make the call to "account/verify_credentials" and to "account/ > rate_limit_status". I got my account info ok, which means that the > request was authenticated, but the rate limit was still 150 but with > less remaining request (2 to be exact). > > There is no question about whether or not I am authenticated, because > I call other API resources that require authentication and I always > get the data with a 200 http status header, but the maximum hourly > requests stay at 150 and the remaining requests go down after each > call. I'm guessing that it may not stop at 150 on authenticated > requests but I'd hate to have to sit here and click through my app 150 > times to find out. > > Alin > > PS Why would you think I was talking about signing in on twitter.com > when I was talking about verifying credential? > > On Apr 11, 10:11 pm, Arnaud Meunier <[email protected]> wrote: > > Hey Alin, > > > > What do you mean by "*I authenticated, verified the credentials and ** > > queried*"? In this context (API call) authenticating means signing your > > request using OAuth. Signing-in with your account on twitter.com is a > > completely different thing and has no effect on your API requests. > > > > Arnaud / @rno <http://twitter.com/rno> > > > > > > > > > > > > > > > > On Mon, Apr 11, 2011 at 12:48 PM, impeto <[email protected]> wrote: > > > Hey guys, > > > > > maybe this question has been asked before, but I just joined the > > > group. I just ran into a little problem that threw me off. I'm > > > developing a website that uses the REST API extensively. The > > > documentation says that anonymous requests get limited to 150 requests/ > > > hour/IP and authenticated requests get limited to 350 requests/hour/ > > > user. I did the anonymous request to "account/rate_limit_status" and I > > > got 150; and then I authenticated, verified the credentials and > > > queried "account/rate_limit_status" again. Got the same result. Why is > > > that? When you are authenticated, aren't you supposed to get 350 back > > > from "account/rate_limit_status"? > > > > > Thanks in advance. > > > > > Alin > > > > > -- > > > Twitter developer documentation and resources: > http://dev.twitter.com/doc > > > API updates via Twitter:http://twitter.com/twitterapi > > > Issues/Enhancements Tracker: > > >http://code.google.com/p/twitter-api/issues/list > > > Change your membership to this group: > > >http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
