429
Too Many Requests
The client has sent too many requests in a given time window. The server is rate limiting to protect itself from being overwhelmed. The Retry-After header usually indicates when to try again.
What does HTTP 429 mean?
The client has sent too many requests in a given time window. The server is rate limiting to protect itself from being overwhelmed. The Retry-After header usually indicates when to try again.
Common causes
- 1
Your application is making API calls faster than the rate limit allows — e.g., more than 100 requests per minute.
- 2
Multiple clients share the same API key or IP address, and their combined traffic exceeds the limit.
- 3
A bug causes a retry loop or rapid polling, sending requests much faster than intended.
How to fix it
- 1
Check the Retry-After header in the response. Wait that many seconds before retrying. Implement exponential backoff in your retry logic.
- 2
Reduce request frequency. Cache responses, batch operations, or use webhooks instead of polling.
- 3
If you need a higher rate limit, check if the API offers a higher tier. Distribute requests across multiple API keys or IP addresses if allowed.
Monitor for HTTP 429 errors
Uptrack uses reasonable check intervals (30s minimum) that stay well within rate limits of virtually all services. If your own API starts returning 429 to legitimate traffic, Uptrack alerts you to the rate limiting issue.
Catch HTTP errors before your users do
20 monitors free — 10 at 30s, 10 at 1min. No credit card required.
Start Monitoring Free