REQUEST_BODY_TOO_LARGE
The request body exceeds the maximum allowed size of ‹max size›.
Category: General
| HTTP status | 413 Content Too Large |
| Retry | After fixing the cause |
When it happens
The request body is larger than the API accepts. It is rejected before being read. error.details carries max_size_formatted, max_size_bytes and request_size_bytes.
How to fix it
Send a smaller body: split a large batch into several calls. For files, use the upload operations, which have their own limits.
Retry
Not as is: the same request fails the same way. Fix the cause described above, then send the request again, under a new Idempotency-Key if the body changed.
Example response
When this error occurs, the API answers 413 Content Too Large with a JSON body of this shape:
{
"type": "https://docs.beel.es/errors/REQUEST_BODY_TOO_LARGE",
"title": "REQUEST_BODY_TOO_LARGE",
"detail": "The request body exceeds the maximum allowed size of ‹max size›.",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "REQUEST_BODY_TOO_LARGE",
"message": "The request body exceeds the maximum allowed size of ‹max size›.",
"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.
Placeholders are filled in at runtime:
‹max size›— the maximum body size, formatted for display.
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