REPRESENTATION_NOT_FOUND
There is no representation document. Generate one before continuing.
Category: VeriFactu
| HTTP status | 400 Bad Request |
| Retry | After fixing the cause |
When it happens
No representation document has been generated for the company, so there is nothing to download.
How to fix it
Generate the representation document first.
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.
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_FOUND",
"title": "REPRESENTATION_NOT_FOUND",
"detail": "There is no representation document. Generate one before continuing.",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "REPRESENTATION_NOT_FOUND",
"message": "There is no representation document. Generate 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_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.
Keep exploring
REPRESENTATION_NOT_ACTIVE
There is no active representation document. Generate and sign one before continuing.
REQUEST_BLOCKED
A security filter at the edge rejected this request before the API saw its body. This usually happens because a text field contains something that looks like code or markup (HTML tags, scripts). Review the request body and try again.