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.
Sending a Tweet does not count against your rate limit of 350 per
hour. However, there are a mximum number of Tweets you can make from
an account at 1000 per day. There are also limits on how many Tweets
you can send per hour and also how many you could do over several
minutes. I'm not sure if
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
If I understand you correctly, you want to build in some sort of
interface into your site to allow users to Tweet from it under their
own accounts. You would use oAuth to set up the credentials.
Establishing these credentials would not count towards the rate limit
as it is done through the Twitter
Thank you very much..
yes you understood my exact requirement.
It is said that POST api calls are not rate limited.. sending tweets is a
POST call. so it should not be rate limited. Am I right?
What is the api call to post a tweet? I think POST statuses/update is used
to post a tweet and it is non
