Uhm... wait a second.................. I distinctly remember you guys (Raffi, I think I'm looking at you) said that secondary rate limits were dropped completely.
On Apr 13, 8:32 pm, Dana Contreras <d...@twitter.com> wrote: > We've added a new set of HTTP response headers to users/search to document > its secondary rate limit: > > * X-FeatureRateLimit-Limit > * X-FeatureRateLimit-Remaining > * X-FeatureRateLimit-Reset > * X-FeatureRateLimit-Class > > Calls to users/search are rate limited by the standard REST API rate limit, > as well as by a secondary rate limit that applies only to users/search (60 > calls per hour). If either of these limits is exceeded, access to > users/search is restricted until the limits reset. > > The new headers provide information about the secondary rate limit in the > same way that the existing X-RateLimit headers document the standard REST > API rate limit. Both sets of headers will be sent in response to calls to > users/search. > > You can find more information about this update > here:https://apiwiki.twitter.com/Rate-limiting > > -- > Dana Contreras > Twitter Platform Teamhttp://twitter.com/DanaDanger -- To unsubscribe, reply using "remove me" as the subject.
