SIN_DESTINATARIO_RESOLUBLE
There is no recipient to send the automatic email to. Add an email to the customer or turn off automatic sending.
Category: Email delivery
| HTTP status | 422 Unprocessable Content |
| Retry | After fixing the cause |
When it happens
The recurring invoice has send_automatically on, but there is nobody to send it to: email_configuration.recipients is empty and the recipient has no email. Without this check, every generated invoice would silently fail to send.
How to fix it
Add email_configuration.recipients, give the customer an email, or set send_automatically to false.
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.
Returned by
The operations where this code is most likely. The list is not exhaustive.
POST /v1/companies/{company_id}/recurring-invoicesPATCH /v1/companies/{company_id}/recurring-invoices/{recurring_invoice_id}POST /v1/companies/{company_id}/recurring-invoices/derivations
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/SIN_DESTINATARIO_RESOLUBLE",
"title": "SIN_DESTINATARIO_RESOLUBLE",
"detail": "There is no recipient to send the automatic email to. Add an email to the customer or turn off automatic sending.",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "SIN_DESTINATARIO_RESOLUBLE",
"message": "There is no recipient to send the automatic email to. Add an email to the customer or turn off automatic sending.",
"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.