// Client error
429 Too Many Requests
The caller has sent too many requests within the server's rate policy. The response may include Retry-After.
Common causes
- A burst exceeds the caller's rate limit.
- Parallel clients share the same quota.
- An automated retry loop amplifies traffic.
Troubleshooting
- Honor Retry-After when supplied; it can be seconds or an HTTP date.
- Use bounded backoff with jitter and reduce concurrency.
- Check whether a quota resets automatically. Retry POST only when duplicate effects are prevented.
HTTP example
POST /payments HTTP/1.1
Host: api.example.com
Content-Type: application/json
{"amount":4900,"currency":"EUR"}
HTTP/1.1 429 Too Many Requests
Retry-After: 60
Content-Type: application/json
Cache-Control: no-store
{"code":"rate_limited","message":"Retry after the indicated delay"}Related status codes
// GET STARTED
Inspect the complete API response.
Use REST Test to send a request and review its status, headers, timing and body together.