FIELD_TOO_LONG
The field '‹value›' cannot exceed ‹value› characters.
Category: General
| HTTP status | 422 Unprocessable Content |
| Retry | After fixing the cause |
When it happens
A text field is longer than it may be. The message names the field and its maximum length.
How to fix it
Shorten the field to the maximum the message gives and send the request again.
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 422 Unprocessable Content with a JSON body of this shape:
{
"type": "https://docs.beel.es/errors/FIELD_TOO_LONG",
"title": "FIELD_TOO_LONG",
"detail": "The field '‹value›' cannot exceed ‹value› characters.",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "FIELD_TOO_LONG",
"message": "The field '‹value›' cannot exceed ‹value› characters.",
"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.
CONCURRENT_MODIFICATION
The resource was modified by another operation. Please retry.
CONFIGURATION_INVALID
The configuration is not valid