PDF_SIGNATURE_INVALID
The signed PDF is not valid: ‹value›
Category: VeriFactu
| HTTP status | 400 Bad Request |
| Retry | After fixing the cause |
When it happens
The uploaded PDF carries no valid electronic signature.
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.
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/PDF_SIGNATURE_INVALID",
"title": "PDF_SIGNATURE_INVALID",
"detail": "The signed PDF is not valid: ‹value›",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "PDF_SIGNATURE_INVALID",
"message": "The signed PDF is not valid: ‹value›",
"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.
Placeholders like
‹value›are filled in at runtime with the actual values of your request.
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.