429 - Too Many Requests
Description
The client has sent too many requests in a given amount of time. This response indicates that the client is exceeding the rate limits configured for the API. The server enforces rate limiting to ensure fair usage and protect against abuse.
Common Scenarios
Rapid successive requests : The client is sending requests faster than the rate limit allows.
Polling without backoff : The client is repeatedly polling an endpoint without implementing exponential backoff.
Concurrent requests : Multiple concurrent requests from the same client exceed the rate limit quota.
Burst traffic : A sudden spike in request volume exceeds the allowed threshold within the time window.
Resolution Steps
Implement exponential backoff in your client to retry requests with increasing delays.
Reduce the frequency of requests to stay within the rate limits.
Review the API documentation for rate limit thresholds and quotas applicable to your account.
Consider caching responses locally to reduce the number of requests needed.
If you require higher rate limits, contact support to discuss your use case.
Refer to the API documentation for rate limiting policies, quota information, and best practices for handling rate limit responses.