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
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:
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
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
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
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
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
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
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
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
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
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
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
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,
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
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
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
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
18 matches
Mail list logo
