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> > > > > > Will you be changing the REST API error code to match the Search API? > > RE: 420 = rate limit exceeded. > > > On Dec 22, 4: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!
