RATE_LIMIT_EXCEEDED
You have exceeded the request rate limit. Wait the seconds given in the Retry-After header and try again.
Category: General
| HTTP status | 429 Too Many Requests |
| Retry | Yes, unchanged |
When it happens
You sent more requests than your rate-limit tier allows in its 60-second window. It can happen on any operation. Most endpoints count per API key; the strict and global tiers count per originating IP.
How to fix it
Wait the seconds in Retry-After, then retry. Spread bursts out, and use bulk operations where they exist instead of one call per item.
Retry
Retry the same request unchanged, with the same Idempotency-Key if you sent one. Wait first, and honour the Retry-After header when the response carries it.
Example response
When this error occurs, the API answers 429 Too Many Requests with a JSON body of this shape:
{
"type": "https://docs.beel.es/errors/RATE_LIMIT_EXCEEDED",
"title": "RATE_LIMIT_EXCEEDED",
"detail": "You have exceeded the request rate limit. Wait the seconds given in the Retry-After header and try again.",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "RATE_LIMIT_EXCEEDED",
"message": "You have exceeded the request rate limit. Wait the seconds given in the Retry-After header and try again.",
"details": {}
},
"meta": {
"timestamp": "2026-05-21T10:00:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}The type URI is stable and always resolves to this page.
Message
Send the request with Accept-Language: <es|en|ca> to receive the message in your preferred language.
Other errors in this category
AUTOMATIC_EMAIL_CONFIG_INVALID
For automatic sending, you must provide an email configuration or a client with email
BAD_REQUEST
The provided data is not valid.
BUSINESS_RULE_VIOLATION
The operation breaks a business rule.
CITY_EMPTY
City cannot be empty
CITY_MAX_LENGTH
City cannot exceed ‹value› characters