REPRESENTATION_ALREADY_ACTIVE
There is already an active representation document. Cancel it before generating another one.
Category: VeriFactu
| HTTP status | 400 Bad Request |
| Retry | No |
When it happens
The company already has an active representation document, so a new one is not generated.
How to fix it
Use the active one. To replace it, cancel it first and then generate a new one.
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 400 Bad Request with a JSON body of this shape:
{
"type": "https://docs.beel.es/errors/REPRESENTATION_ALREADY_ACTIVE",
"title": "REPRESENTATION_ALREADY_ACTIVE",
"detail": "There is already an active representation document. Cancel it before generating another one.",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "REPRESENTATION_ALREADY_ACTIVE",
"message": "There is already an active representation document. Cancel it before generating another one.",
"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
ALREADY_REGISTERED
The NIF is already registered in VeriFactu
API_COMMUNICATION_ERROR
Error communicating with the VeriFactu API
COMPANY_NIF_MISSING
The issuing company has no NIF configured. Set the NIF before submitting invoices to VeriFactu
ENV_MISMATCH
API key does not match NIF environment: use a live key for production NIFs and a test key for sandbox NIFs
NIF_NOT_CONFIGURED
The profile has no NIF. Complete it before continuing.