REPRESENTATION_NOT_ACTIVE
There is no active representation document. Generate and sign one before continuing.
Category: VeriFactu
| HTTP status | 400 Bad Request |
| Retry | No |
When it happens
The company has no active representation document (generated and signed), so there is nothing to cancel.
How to fix it
Check the representation's status. Nothing needs cancelling if none is active.
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_NOT_ACTIVE",
"title": "REPRESENTATION_NOT_ACTIVE",
"detail": "There is no active representation document. Generate and sign one before continuing.",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "REPRESENTATION_NOT_ACTIVE",
"message": "There is no active representation document. Generate and sign one before continuing.",
"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_DISABLED
VeriFactu is already disabled for this user
ALREADY_ENABLED
VeriFactu is already enabled for this user
ALREADY_REGISTERED
The NIF is already registered in VeriFactu
API_COMMUNICATION_ERROR
Error communicating with the VeriFactu API
API_KEY_NOT_CONFIGURED
The VeriFactu API key has not been configured