INVOICE_REPLY_DUPLICATE
A reply with this channel and external identifier already exists.
Category: Customer replies
| HTTP status | 409 Conflict |
| Retry | No |
When it happens
A reply with the same channel and external_id already exists; error.details.reply_id is its id, absent when that reply was deleted. A deleted reply cannot be registered again.
How to fix it
Nothing to retry: the message is already stored, or was deleted on purpose.
Retry
Do not retry. The outcome is final: sending the same request again gets the same answer.
Returned by
The operations where this code is most likely. The list is not exhaustive.
Example response
When this error occurs, the API answers 409 Conflict with a JSON body of this shape:
{
"type": "https://docs.beel.es/errors/INVOICE_REPLY_DUPLICATE",
"title": "INVOICE_REPLY_DUPLICATE",
"detail": "A reply with this channel and external identifier already exists.",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "INVOICE_REPLY_DUPLICATE",
"message": "A reply with this channel and external identifier already exists.",
"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
INVOICE_REPLY_ATTACHMENT_NOT_FOUND
Invoice reply attachment not found.
INVOICE_REPLY_INVOICE_NOT_ISSUED
Replies can only be registered about an issued invoice: this one is a draft or is scheduled.
INVOICE_REPLY_NOT_FOUND
Invoice reply not found.