NIF_NOT_CONFIGURED
The profile has no NIF. Complete it before continuing.
Category: VeriFactu
| HTTP status | 400 Bad Request |
| Retry | After fixing the cause |
When it happens
The company has no NIF yet, and the operation acts before the AEAT on that NIF.
How to fix it
Complete the company's tax details with its NIF, then repeat the request.
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.
DELETE /v1/companies/{company_id}/representationPOST /v1/companies/{company_id}/representation/submit
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/NIF_NOT_CONFIGURED",
"title": "NIF_NOT_CONFIGURED",
"detail": "The profile has no NIF. Complete it before continuing.",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "NIF_NOT_CONFIGURED",
"message": "The profile has no NIF. Complete it 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