Please implement a better error message than only Too many requests.
Requests exceeding the rate limit will receive a 429 Too Many Requestserror response. The response will also include a Retry-After header that specifies the number of seconds to wait until your next request can be processed. With this information you can implement retry logic as a way to gracefully handle rate limits.
Keep in mind that rate limits apply to all requests, so it would be wise to implement any retry logic at a global level. Otherwise, many requests sent around the same time will all be rate-limited and will all retry at the same time, which will cause many of them to be rate limited again.
Implement that time is visible, ike Error: too many request. Wait xx seconds before you retry.
Implement auto retry if down to a second.
Please implement a better error message than only Too many requests.
Requests exceeding the rate limit will receive a 429 Too Many Requestserror response. The response will also include a Retry-After header that specifies the number of seconds to wait until your next request can be processed. With this information you can implement retry logic as a way to gracefully handle rate limits.
Keep in mind that rate limits apply to all requests, so it would be wise to implement any retry logic at a global level. Otherwise, many requests sent around the same time will all be rate-limited and will all retry at the same time, which will cause many of them to be rate limited again.
Implement that time is visible, ike Error: too many request. Wait xx seconds before you retry.
Implement auto retry if down to a second.