Thanks for the reply. Need some more clarification. My web application enable user to tweet in their twitter accounts. A user can tweet after he is logged in and authorizes my app. So asking login credentials and autorizing my application requires some api calls. Will these be counted under rate limiting?
On Nov 16, 7:25 pm, Red_Eyes <millerdotp...@googlemail.com> wrote: > You can make a call to search, for example, both authenticated and > unauthenticated. Search uses a different rate limiting system to most > other API calls. You have your assumption the wrong way round, though. > When you are authenticated, generally you will get around 350 API > calls per hour allowed. When you are unauthenticated, you will get 150 > per hour. Be aware, though, 2 people on the same IP performing an > unauthentiacted API call will share the same pool of 150 hits. 2 > people on the same IP but each authenticated will get roughly 350 hits > each. Be aware, though, on peak demands, Twitter can lower the amount > of hits dynamically. Also note, if you use multiple accounts to try > and circumvent the rate limits, the chances are you will get spotted > and blocked! > > Red > > On Nov 16, 1:31 pm, Ganesh Peria <periagan...@gmail.com> wrote: > > > Hi, > > Im new to Twitter API. while reading the rate limiting faq, it is > > said that authenticated api calls are counted under IP address and > > unauthenticated api calls are counted under the logged in user. > > > My question is what is authenticated call and an unauthenticated > > call. > > > My assumption is this: In the api documentation if it says "Requires > > Authentication =true" then is an authenticated call otherwise an > > unauthenticated call. Am I right? -- 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
