| Previous | Next |
| HTTP_STATUS_PRECONDITION_REQUIRED | HTTP_STATUS_HEADER_FIELDS_TOO_LARGE_2 |
HTTP_STATUS_TOO_MANY_REQUESTS
The limit may apply to an account, IP address, token, endpoint, or shared resource. A response can include Retry-After, but its absence does not mean immediate repeated retries are safe.
Implement bounded backoff, honor documented quotas, and avoid concurrent retry storms. Server logs or rate-limit headers are needed to identify the exact scope of the limit.
A 429 response can apply to a user, token, IP address, tenant, route, or another server-defined quota. Honor Retry-After when present and reduce request concurrency or frequency according to the API contract. Immediate parallel retries usually extend the throttling period and add avoidable load.
Looking for a different code? Search another status or error code.