#1

I’m thinking of developing an application that uses “Search Tweets” in Twitter’s Public API.
Question 1 … Shouldn’t the Rate Limits be exceeded?
Question 2 … What happens if Rate Limits are exceeded?
(Example: Response becomes an error, but when the time limit has passed, the response can be obtained normally)
(Example: An error occurs in the response and the Twitter account is suspended.)

I know that “Search Tweets” has Rate Limits.

180 Requests / 15-min window (user auth)

I understand the Developer Agreement.
In the “Rate Limits.” Section, there is a description that Rate Limits must not be exceeded, but the event when it was exceeded could not be read.

That’s all for the question. Thank you.

#2

Thanks for writing in here. Have you seen this page in our documentation on rate limiting? Typically when you hit the rate limits, you get an error message. Let me know if you have further questions.

1 Like
#3

Thank you for your reply.

I read the documentation on rate limiting.
I returned error code 88 and realized that my account would not be banned immediately.

There are further questions.
I want to develop an application that uses “Search Tweets”.
If you search for more than 18,000 search results, you may violate Rate Limit.
(I understand that if you specify 100 in the parameter count, 18,000 tweets will be the upper limit by “100 tweets x 180 requests”.)
Is it possible to ban even if it is implemented to repeat the search and return to error code 88 when the process is completed?
Or do you need to check “x-rate-limit-remaining” every time and monitor to avoid returning error code 88?

Thank you.

#4

You are unlikely to get banned for hitting the rate limit occasionally when developing - But it’s definitely better practice to check the HTTP headers x-rate-limit-remaining and stop / wait for the reset time (reset time is in unix epoch x-rate-limit-reset header that can convert to UTC time, it’s also returned in the HTTP headers for each request, and from previous experience, i’d give it an extra 1 or 2 seconds to make sure it’s ready)

1 Like
#5

And what happens, when there are limits but they are not reflected in the documentation, and not headers come in the response? How check limits ?

#6

Unfortunately i think for those it’s just a matter of watching for errors, you get back an HTTP error code, and the body is a twitter error code with a message - here’s the list: Documentation Home | Docs | Twitter Developer Platform

1 Like
#7

I also think that checking the HTTP header “x-rate-limit-remaining” is a good implementation.
However, I would like to understand the penalty for exceeding Rate Limits without implementing an implementation that checks “x-rate-limit-remaining”.
(If you only get an error message temporarily, don’t worry.
But if your account is banned, you need to develop it carefully. )

Is there a document that clearly states the penalty for exceeding the Rate Limits? :thinking:

#8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.