Rate Limit Exceeded
Occurs when the client exceeds the allowed number of API requests per time window.
Cause: Your account has exceeded the per-minute request limit for this endpoint. Limits are shared by all API keys of the account and counted separately for each endpoint. See Rate Limiting for the limit of each endpoint.
Suggested Action: Wait until the rate limit resets (check retry-after seconds or rate-limit-reset timestamp) before making more requests. Consider implementing exponential backoff in your client.
Common Scenarios:
- Sending more requests to one endpoint within a minute than its limit allows (for example more than 100 calls to
/v1/ip-lookup) - Several API keys or processes of the same account calling the same endpoint at once, since they share one limit
- Retrying immediately after a
429instead of waiting forretry-after
Response Example
{
"type": "https://developers.leadboxer.com/docs/rate-limit-exceeded",
"title": "Rate Limit Exceeded",
"status": 429,
"detail": "API rate limit exceeded",
"instance": "/v1/user-datasets",
"retry-after": 43,
"rate-limit": 30,
"rate-limit-remaining": 0,
"rate-limit-period": "minute",
"rate-limit-reset": 1766565255
}HTTP Status
429 Too Many Requests
Additional Fields
retry-after: Wait time in seconds before retryingrate-limit: Maximum allowed requests in the periodrate-limit-remaining: Request remaining in a windowrate-limit-period: Time window (alwaysminute)rate-limit-reset: Unix timestamp (seconds) when the window resets
Updated 5 days ago
Did this page help you?
