Re: [twitter-dev] Rate limiting questions
Hi there,
This is actually a different error than your library may be leading you to
believe -- the library is suggesting that the 403 may be due to rate
limiting, but in this case it's actually due to a recent permission model
change.
The permission model gas change whereas requesting a user's direct messages
now requires a re-authorization at the appropriate access request level
(RWD). You can read more about the new permission model and what to do next
here: http://dev.twitter.com/pages/application-permission-model ..
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Tue, Jul 5, 2011 at 1:35 PM, YupiqDZ mrclea...@gmail.com wrote:
Hi,
I'm currently in the process of writing an application which
periodically gets directed messages from a user (once every 120
seconds checks if the user has new messages).
The API I am using is the Twitter4j library in Java. Here's the error
I get:
403:The request is understood, but it has been refused. An
accompanying error message will explain why.
TwitterException{exceptionCode=[ece01d6a-01eb72d6], statusCode=403,
retryAfter=0,
rateLimitStatus=RateLimitStatusJSONImpl{remainingHits=326,
hourlyLimit=350, resetTimeInSeconds=1309899, secondsUntilReset=1629,
resetTime=Tue Jul 05 13:58:10 PDT 2011}, version=2.1.10}
I am confused as to how my remainingHIts is still 326 yet I am rate
limited? Additionally, even if I wait until the reset time indicated
before hitting the service again, I receive the rate limit exception
again with the reset time pushed back by an hour.
I am fairly confident that this service does not poll Twitter more
than 350 times a second, is there something else that could be causing
me to be rate limited?
Thanks
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] rate limiting due to invalid oauth credentials
Authenticated Rate Limit --- 350 Calls per hour. Unauthenticated Rate Limit --- 150 Calls per hour. Please read the docs. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] rate limiting on users profile image
DT :
http://dev.twitter.com/pages/rate-limiting#rest
API methods which are not directly rate limited are still subject to
organic, unpublished limits. This includes actions like publishing status
updates, direct messages, follow/unfollow actions, etc. These Twitter
Limitshttp://support.twitter.com/forums/10711/entries/15364 are
described on our help site
I think this says it all.
--Regards,
Denzil
On Wed, Jun 8, 2011 at 11:26 PM, dt dtip...@gmail.com wrote:
According to the current docs, the users/profile_image path is not
currently rate limited:
http://dev.twitter.com/doc/get/users/profile_image/:screen_name
But when I access this method, I'm sometimes getting rate limit
errors:
{error:Rate limit exceeded. Clients may not make more than 150
requests per hour.,request:\/1\/users\/profile_image\/tw.json?
size=bigger}
Has this policy been updated, and the docs are behind? (I work in a
place where a single IP is shared for the whole building, so rate
limits are exceeded a lot of the time when I'm testing)
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] rate limiting on users profile image
Hey,
This endpoint has always been rate limited so this is an error in the docs.
We have some updates to the docs coming out soon which will correct that.
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Wed, Jun 8, 2011 at 10:56 AM, dt dtip...@gmail.com wrote:
According to the current docs, the users/profile_image path is not
currently rate limited:
http://dev.twitter.com/doc/get/users/profile_image/:screen_name
But when I access this method, I'm sometimes getting rate limit
errors:
{error:Rate limit exceeded. Clients may not make more than 150
requests per hour.,request:\/1\/users\/profile_image\/tw.json?
size=bigger}
Has this policy been updated, and the docs are behind? (I work in a
place where a single IP is shared for the whole building, so rate
limits are exceeded a lot of the time when I'm testing)
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] rate limiting on users profile image
Matt :
Can you also clear the air on what the snippet from the Twitter docs mean? I
read it as there are no non-rate limited methods.
http://dev.twitter.com/pages/rate-limiting#rest
API methods which are not directly rate limited are still subject to
organic, unpublished limits. This includes actions like publishing status
updates, direct messages, follow/unfollow actions, etc. These Twitter
Limitshttp://support.twitter.com/forums/10711/entries/15364 are
described on our help site
--Regards,
Denzil
On Thu, Jun 9, 2011 at 12:45 AM, Matt Harris thematthar...@twitter.comwrote:
Hey,
This endpoint has always been rate limited so this is an error in the docs.
We have some updates to the docs coming out soon which will correct that.
Best,
@themattharrishttps://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Wed, Jun 8, 2011 at 10:56 AM, dt dtip...@gmail.com wrote:
According to the current docs, the users/profile_image path is not
currently rate limited:
http://dev.twitter.com/doc/get/users/profile_image/:screen_name
But when I access this method, I'm sometimes getting rate limit
errors:
{error:Rate limit exceeded. Clients may not make more than 150
requests per hour.,request:\/1\/users\/profile_image\/tw.json?
size=bigger}
Has this policy been updated, and the docs are behind? (I work in a
place where a single IP is shared for the whole building, so rate
limits are exceeded a lot of the time when I'm testing)
--
Twitter developer documentation and resources:
https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] rate limiting on users profile image
Hi Denzil,
The paragraph is letting you know that the API isn't the only source of rate
limits. If an API method says it isn't rate limited it means the request
will not count against the 350 authenticated (150 unauthenticated) requests
you are permitted per hour.
It doesn't mean the method isn't limited in some way though. In the text we
link to the page on our Twitter help site which explains the other limits
which exist on Twitter. Those limits are often referred to as user limits
and apply to the user no matter what application or site they are using
(including twitter.com).
The user limits are described on more detail on the help site (linked to
from the rate limiting document):
https://support.twitter.com/forums/10711/entries/15364
Best,
@themattharris https://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Wed, Jun 8, 2011 at 1:40 PM, Correa Denzil mcen...@gmail.com wrote:
Matt :
Can you also clear the air on what the snippet from the Twitter docs mean?
I read it as there are no non-rate limited methods.
http://dev.twitter.com/pages/rate-limiting#rest
API methods which are not directly rate limited are still subject to
organic, unpublished limits. This includes actions like publishing status
updates, direct messages, follow/unfollow actions, etc. These Twitter
Limits http://support.twitter.com/forums/10711/entries/15364 are
described on our help site
--Regards,
Denzil
On Thu, Jun 9, 2011 at 12:45 AM, Matt Harris thematthar...@twitter.comwrote:
Hey,
This endpoint has always been rate limited so this is an error in the
docs. We have some updates to the docs coming out soon which will correct
that.
Best,
@themattharrishttps://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Wed, Jun 8, 2011 at 10:56 AM, dt dtip...@gmail.com wrote:
According to the current docs, the users/profile_image path is not
currently rate limited:
http://dev.twitter.com/doc/get/users/profile_image/:screen_name
But when I access this method, I'm sometimes getting rate limit
errors:
{error:Rate limit exceeded. Clients may not make more than 150
requests per hour.,request:\/1\/users\/profile_image\/tw.json?
size=bigger}
Has this policy been updated, and the docs are behind? (I work in a
place where a single IP is shared for the whole building, so rate
limits are exceeded a lot of the time when I'm testing)
--
Twitter developer documentation and resources:
https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources:
https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Rate limiting - per user or per application key?
Per user per application. A user can use, for example, 350 requests with TweetDeck, and then it can still use 350 requests with your application, without interfering with other users that also use your application. Tom On 5/31/11 2:37 PM, Rob Wilson wrote: Hi, I am writing an iPhone application that uses the Twitter API, using oAuth. Could you please clarify that the 350 requests per hour are tied to the logged in user and not the application key? If not, do I need to white-list to prevent this becoming a problem? Cheers, Rob. -- Please visit... SpikyOrange.co.uk http://spikyorange.co.uk/ A portal for anything I create, including... BitBanter.com http://bitbanter.com/ A technical podcast 50% Tech + 50% software development = 100% Entertaining! http://spikyorange.co.uk/ -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk https://groups.google.com/forum/#%21forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Rate limiting - per user or per application key?
Perfect - thanks Tom. On 31 May 2011 13:39, Tom van der Woerdt i...@tvdw.eu wrote: Per user per application. A user can use, for example, 350 requests with TweetDeck, and then it can still use 350 requests with your application, without interfering with other users that also use your application. Tom On 5/31/11 2:37 PM, Rob Wilson wrote: Hi, I am writing an iPhone application that uses the Twitter API, using oAuth. Could you please clarify that the 350 requests per hour are tied to the logged in user and not the application key? If not, do I need to white-list to prevent this becoming a problem? Cheers, Rob. -- Please visit... SpikyOrange.co.uk http://spikyorange.co.uk/ A portal for anything I create, including... BitBanter.com http://bitbanter.com/ A technical podcast 50% Tech + 50% software development = 100% Entertaining! http://spikyorange.co.uk/ -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Please visit... SpikyOrange.co.uk http://spikyorange.co.uk/ A portal for anything I create, including... BitBanter.com http://bitbanter.com/ A technical podcast 50% Tech + 50% software development = 100% Entertaining! http://spikyorange.co.uk/ -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Rate limiting for streaming API
On 2/19/11 1:49 PM, Paresh Nakhe wrote: Hi, From what i understand, there is no concept of rate limiting for streaming api. Actually it does make sense because if anyone is to use 'statuses/sample' method (say) the limit will soon be crossed. We are working on something that will heavily use the streaming api, so if rate limiting is imposed in future it could create some problems. Are there any chances of such a restriction being imposed? There's no limit on the amount of tweets you can receive, but there's a limit on the amount of searches you can do, and the amount of connections you can have open. Secondly, this api requires authentication unlike search api. Authentication for user streams is fine but I don't understand it's need for streaming api. There's probably no real technical reason for why this is required, but for properly being able to keep statistics etc, it's needed. That, and the fact that there are several different levels of access to the API. Thanks, Paresh -- 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
Re: [twitter-dev] Rate limiting for streaming API
On going through the documentation in more detail i found this: - The the track parameter (keywords), and the location parameter (geo) on the statuses/filter method are rate-limited predicates. - After the * limitation period* expires, all matching statuses will once again be delivered, along with a limit message that enumerates the total number of statuses that have been eliminated from the stream since the start of the connection. What exactly is the limitation period and what is one supposed to do after the limitation period expires? Destroy the current connection and create a new one? Paresh. On Sat, Feb 19, 2011 at 6:22 PM, Tom van der Woerdt i...@tvdw.eu wrote: On 2/19/11 1:49 PM, Paresh Nakhe wrote: Hi, From what i understand, there is no concept of rate limiting for streaming api. Actually it does make sense because if anyone is to use 'statuses/sample' method (say) the limit will soon be crossed. We are working on something that will heavily use the streaming api, so if rate limiting is imposed in future it could create some problems. Are there any chances of such a restriction being imposed? There's no limit on the amount of tweets you can receive, but there's a limit on the amount of searches you can do, and the amount of connections you can have open. Secondly, this api requires authentication unlike search api. Authentication for user streams is fine but I don't understand it's need for streaming api. There's probably no real technical reason for why this is required, but for properly being able to keep statistics etc, it's needed. That, and the fact that there are several different levels of access to the API. Thanks, Paresh -- 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 -- *What I have is not a dream, because I will make it a reality.* -- 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
Re: [twitter-dev] Rate limiting for streaming API
On Sat, Feb 19, 2011 at 7:52 AM, Tom van der Woerdt i...@tvdw.eu wrote: On 2/19/11 1:49 PM, Paresh Nakhe wrote: Hi, From what i understand, there is no concept of rate limiting for streaming api. Actually it does make sense because if anyone is to use 'statuses/sample' method (say) the limit will soon be crossed. We are working on something that will heavily use the streaming api, so if rate limiting is imposed in future it could create some problems. Are there any chances of such a restriction being imposed? There's no limit on the amount of tweets you can receive, but there's a limit on the amount of searches you can do, and the amount of connections you can have open. Responses here from Twitter staff and notes in the docs say that the sample (default) level of delivery is limited to 1% of all tweets. As long as your total flow is less than 1% of the firehose (all tweets) you are supposed to receive every tweet that matches your search terms. From my experience, you only receive about 95% of the tweets that match a set of search terms. I've never used a set of search terms that delivered anywhere near 1% of the total flow. Here are some numbers: - The total flow of all tweets is in the order of magnitude of 100,000,000 per day. - The sample stream should thus receive up to 1,000,000 tweets per day. - When I collect tweets based on search words that deliver about 10,000 tweets a day, I don't receive about 5% of the tweets that do match these terms. If getting *every* tweet that matches these terms is essential, I recommend combining streaming with backfilling. By backfilling I mean using the search API or timeline calls in the REST API to collect tweets that may have been missed by the streaming API. The result is real-time delivery of 95% of the tweets you need and eventual delivery of the remainder. Don't bother asking about future restrictions. That question will not be answered by Twitter HQ. -- 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
Re: [twitter-dev] Rate limiting for streaming API
On 2/19/11 2:23 PM, Paresh Nakhe wrote: On going through the documentation in more detail i found this: - The the track parameter (keywords), and the location parameter (geo) on the statuses/filter method are rate-limited predicates. You can't have an infinite number of search terms. - After the */limitation period/* expires, all matching statuses will once again be delivered, along with a limit message that enumerates the total number of statuses that have been eliminated from the stream since the start of the connection. As far as I know, this limitation is only for user streams. When you get more than 2 or 3 statuses per second, it wouldn't be readable for the user anyway so the extra statuses get discarded and you get a limitation notice. I don't think that this goes for the normal stream. What exactly is the limitation period and what is one supposed to do after the limitation period expires? Destroy the current connection and create a new one? Just keep listening :-) Paresh. On Sat, Feb 19, 2011 at 6:22 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: On 2/19/11 1:49 PM, Paresh Nakhe wrote: Hi, From what i understand, there is no concept of rate limiting for streaming api. Actually it does make sense because if anyone is to use 'statuses/sample' method (say) the limit will soon be crossed. We are working on something that will heavily use the streaming api, so if rate limiting is imposed in future it could create some problems. Are there any chances of such a restriction being imposed? There's no limit on the amount of tweets you can receive, but there's a limit on the amount of searches you can do, and the amount of connections you can have open. Secondly, this api requires authentication unlike search api. Authentication for user streams is fine but I don't understand it's need for streaming api. There's probably no real technical reason for why this is required, but for properly being able to keep statistics etc, it's needed. That, and the fact that there are several different levels of access to the API. Thanks, Paresh -- 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 -- /What I have is not a dream, because I will make it a reality./ -- 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
Re: [twitter-dev] Rate Limiting
I'm being locked out on my account using the API and I'm seeing reports from others. At the moment making a request to http://api.twitter.com/version/account/rate_limit_status.json comes back saying I have 8 calls left and it will be reset at 07:54, but the time is currently 13:18! The time for the reset has been the same since at least 8am. Confirming. This seems to have started last night. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Man who live in glass house dress in basement. -
Re: [twitter-dev] Rate Limiting
Quoting Cameron Kaiser spec...@floodgap.com: I'm being locked out on my account using the API and I'm seeing reports from others. At the moment making a request to http://api.twitter.com/version/account/rate_limit_status.json comes back saying I have 8 calls left and it will be reset at 07:54, but the time is currently 13:18! The time for the reset has been the same since at least 8am. Confirming. This seems to have started last night. I saw something similar - erratic behavior when non-authenticated. Normally it says 75 calls per hour, number of calls left and a fair amount of time until reset. But sometimes it jumps down to one second left and stays there, eventually causing a hard rate limit. I haven't tried this morning - I can try again in about two hours.
Re: [twitter-dev] Rate Limiting
Quoting M. Edward (Ed) Borasky zn...@borasky-research.net: Quoting Cameron Kaiser spec...@floodgap.com: I'm being locked out on my account using the API and I'm seeing reports from others. At the moment making a request to http://api.twitter.com/version/account/rate_limit_status.json comes back saying I have 8 calls left and it will be reset at 07:54, but the time is currently 13:18! The time for the reset has been the same since at least 8am. Confirming. This seems to have started last night. I saw something similar - erratic behavior when non-authenticated. Normally it says 75 calls per hour, number of calls left and a fair amount of time until reset. But sometimes it jumps down to one second left and stays there, eventually causing a hard rate limit. I haven't tried this morning - I can try again in about two hours. Now it's solidly refusing to let me access the API: limit: 75, remaining: 0, seconds_to_go: 1, ratio: 0.00, sleep: 1.0 Rate limit exceeded. Clients may not make more than 75 requests per hour. This was on an unauthenticated rate limit status call in Net::Twitter - I'll have to do some digging to get the HTTP data but I can try that later (from a different IP address).
Re: [twitter-dev] Rate Limiting Check
Currently looking more into this. It appears that you're not limited by User or IP but rather a combination of the two. Ryan could you comment on this? Is this the expected behaviour? Scott. On 26 Feb 2010, at 14:06, Scott Wilcox wrote: Hi folks, If you ever bump into rate limiting issues and want to check your remaining balance from a third party site, I've added a small feature to allow you to do so. It'll display your hourly limit, remaining calls, reset time and time from now for reset (ie, 30 minutes). Its pretty much a basic Rate_Limit_Status call made pretty. Simple but effective. Those wishing to use it, simply pop over to https://dor.ky/services/twitter/ratelimit and let me know if you have any issues. Scott. smime.p7s Description: S/MIME cryptographic signature
Re: [twitter-dev] Rate Limiting Twitter
You can check if you are getting rate limited with this method: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0rate_limit_status If you are using OAuth on http://api.twitter.com then 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
Re: [twitter-dev] Rate Limiting question
For the first use case, following many users' timelines, you should be using the follow method on the Streaming API. Currently you cannot get protected and low quality user statuses this way, but you can get the vast majority of tweets this way. Until we support these corner cases, you can fall back to the REST API for protected users. For automated hashtag searching, you should also be using the Streaming API. The track feature will give you all hashtags search for up to a fairly generous proportion of the total stream of tweets. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Fri, Jan 1, 2010 at 2:43 PM, jojet j...@jojet.com wrote: Hi all, I was feeling a little clever after working on some Twitter API stuff but then thought oh! I'd better think about Twitters rate limiting...and then that's where my brain started to melt! A few bits of info: my web app needs people to authenticate (OAUTH) and, from then on, the app analyses their tweets and occasionally updates registered user's statuses. I've applied for the webserver IP to be white listed which I believe gives the app 20,000 requests per hour. I've not found the search API to be great when looking for a hashtag (sometimes tweets just don't seem to get indexed) so I've gone a stage further and am analysing the individual timelines of all my registered users via a cron job (the cron job sucks in all of a persons tweets greater than the last analysed tweet of the user). This call is made via OAUTH/authenticated so I believe such a call depletes the user's rate limit quota rather than the IP/authenticated account of the webserver quota? Is that correct? Thanks for any thoughts here Joel
