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.
On Dec 22 2009, 2:44 pm, Wilhelm Bierbaum <wilh...@twitter.com> wrote:
> 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!
