The documentation states that I can call this endpoint 900 per 15 minute window.
I only need to call it 400 times once an hour, but after between 250/300 calls, I get “Rate limit exceeded” errors and cannot retrieve the information anymore.
Is it app auth or User auth? The rate limits may not be exact up to a few seconds - it’s better to rely on the http response headers instead of assuming the rate limits and reset times - also a bad idea to call this endpont in parallel in different threads - that’s another common issue.
I use app auth. But anyway, the limits are the same for both app auth and user auth.
I didn’t know about the http response headers. I will have a look at it.
I faced the same kind of issue with the Standard search API a few months ago, and I was able to solve it by creating batches of 25 calls each. But this approach doesn’t work with the “GET users/show” endpoint.
Ah yeah - you could batch them and use GET users/lookup | Docs | Twitter Developer Platform too - that would definitely give you more
The “x-rate-limit-limit” in the response headers indicates that the rate limit ceiling for this given endpoint is 300.
How is that possible?
The documentation says it’s 900.
When I use the same credentials for calling “GET search/tweets”, the “x-rate-limit-limit” in the response headers indicates that the rate limit ceiling for this given endpoint is 450, which is expected.
system
Closed
#6
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
