Search API: new HTTP response code 420 for rate limiting starting 1/18/2010

[Wilhelm Bierbaum]

We're changing the response code sent back by the Search API when the

rate limit has been exceeded. At present, it is impossible to

distinguish rate limit responses from other error conditions in

responses from the Search API -- this is what we're trying to fix.

Starting Monday, January 18th, 2010 the Search API will respond 

with error code 420 in the event that the number of requests you have 

made exceeds the quota afforded by your assigned rate limit. 

Please update your response your response handler to accommodate this

new behavior.

Apologies for the false start last time this change was announced.

If you have any questions, please feel free to post them on twitter-development-talk. 

Thanks!

[DustyReagan]

Will you be changing the REST API error code to match the Search API?
RE: 420 = rate limit exceeded.

[Marco Kaiser]

yeah, doesn't make much sense to have two different codes indicating that the limit is exceeded... 

2009/12/23 DustyReagan <dusty...@gmail.com>

[Wilhelm Bierbaum]

Eventually the REST API will return the same 420 response code to
indicate rate limiting. We wanted to change as little as possible to
get people comfortable with the new response code.

On Dec 22, 4:07 pm, Marco Kaiser <kaiser.ma...@gmail.com> wrote:
> yeah, doesn't make much sense to have two different codes indicating that
> the limit is exceeded...
>

> 2009/12/23 DustyReagan <dustyrea...@gmail.com>

[Sandip]

i am getting this response code in my twitter search application, how
to resolve the error ?

[M. Edward (Ed) Borasky]

OK ... next question ... are the rate limit HTTP headers from the REST
API now "ported" to Search and working / documented?

2. HTTP response headers included in all REST API responses which
count against the rate limit:

* X-RateLimit-Limit the current limit in effect
* X-RateLimit-Remaining the number of hits remaining before you
are rate limited
* X-RateLimit-Reset the time the current rate limiting period ends
in epoch time.

[Andy Freeman]

(1) When will http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors
be updated?
(2) How does 420 differ from 400?

> > > > Thanks!- Hide quoted text -
>
> - Show quoted text -

[Abraham Williams]

1) Looks like the docs got updated. 

2) 400 will eventually just be for API calls that are malformed: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1

Abraham

--
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