[twitter-dev] Search API rate limit change?
Hello, After the latest performance issues with the search api i have been seeing a lot of 420 response codes.From yesterday until now i only get 420 responses on the every search i make. In particular, i search for about 100 keywords simultaneously every 6 mins. Why is this happening? Was there any change on the Search API limit? Any help is greatly appreciated. Thanks, Zaver -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Http Response code handling
Hello, I am using the search api with multiple keywords (120 keywords) using curl (curl_multi_init etc.), querying the api every 5 mins and i need some help on how to handle some of the response codes. Specifically: 420 - i get this error on some of my keywords not all. Does this mean that i am rate limited and should wait for the amount of time in the Retry-after part in general or only for these keywords? Currently I do wait for the amount of time it specifies for the whole keyword set. Is that right? Haven't come across these yet although i would like to have some handling for these. 502: Bad Gateway: Twitter is down or being upgraded. 503: Service Unavailable: The Twitter servers are up, but overloaded with requests. Try again later. Any help is greatly appreciated. Thanks Zaver -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Search API rate limit on some keywords
Hello, I am experimenting with the Search API using php curl to get results on multiple keyword searches (about 130). It works fine, although i have observed that sometimes some of the keywords get a 420 code? Any ideas why is this happening? Let me know if you want any more details on my part. Thanks Zaver -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Search API rate limit on some keywords
Thanks for the reply. So as i understand it i am not being rate limited, it just doesn't find any results to return for the specific keywords. In that case should i wait for the amount of time specified on the Retry-after field to make a new search? If i don't wait will that lead to my ip getting blacklisted or it will just not return accurate search results? Thanks in advance. On Feb 2, 3:04 am, @IDisposable idisposa...@gmail.com wrote: have observed that sometimes some of the keywords get a 420 code? Any ideas why is this happening? You get a 420 NOT USED when a search term hasn't been used recently where the recently is whatever small timeframe (sometimes 7 days, often less) is currently available in the search index. I get it all the time for things like #stlcards :) -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk