FILE_TOO_LARGE
File is too large. Maximum allowed size: ‹value›
Category: General
| HTTP status | 422 Unprocessable Content or 413 Content Too Large |
HTTP status
This code can arrive with 422 Unprocessable Content or 413 Content Too Large, depending on the operation. Branch on error.code, not on the status alone.
Example response
When this error occurs, the API returns a JSON response with the following shape:
{
"type": "https://docs.beel.es/errors/FILE_TOO_LARGE",
"title": "FILE_TOO_LARGE",
"detail": "File is too large. Maximum allowed size: ‹value›",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "FILE_TOO_LARGE",
"message": "File is too large. Maximum allowed size: ‹value›",
"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 like
‹value›are filled in at runtime with the actual values of your request.
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