Update VeriFactu configuration
Scopeconfiguration:writeDeprecated. Use PUT /v1/companies/{company_id}/verifactu-configuration, which
behaves identically.
Updates the VeriFactu configuration of the company (NIF) in focus.
- Writable fields: only
enabledandapply_by_default. The rest of the returned configuration (status,signed,activated,nif_status) is resolved server-side. - Full replacement: both fields are required — this PUT replaces the whole state, it
is not a partial merge, so omitting one is a client error and not a silent
false. - Coherence: if
enabledis false,apply_by_defaultmust be false too. The other way round answers422APPLY_BY_DEFAULT_REQUIRES_ENABLED.
Turning it off
Setting enabled to false stops sending invoices to the AEAT and starts the
deregistration of the NIF with the VeriFactu provider. It does not deactivate the
NIF: the activation is a fact of its own for the (company, environment) pair, so issuing
carries on and issuing-readiness stays ready. Releasing the NIF is always
DELETE /v1/companies/{company_id}/activations, with its own guarantees.
Keys are prefixed beel_sk_, and each one carries the scopes it was created with: a key
short of the scope an operation needs is answered 403. The scope an operation requires
is shown next to its title, and the full catalogue lives in the Scopes reference.
Keys are created from the BeeL dashboard. They are secret credentials: do not share them or commit them to source control.
In: header
Whether VeriFactu is enabled for this user. When enabled, the user can submit invoices to AEAT. Freelancers who don't need to submit invoices to AEAT can leave it disabled.
Whether VeriFactu should be automatically applied to new invoices. Requires 'enabled' to be true.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X PUT "https://app.beel.es/api/v1/configuration/verifactu" \ -H "Content-Type: application/json" \ -d '{ "enabled": true, "apply_by_default": true }'{
"success": true,
"data": {
"enabled": false,
"apply_by_default": false,
"nif_status": "PENDING",
"nif_registered_at": "2019-08-24T14:15:22Z",
"status": "DISABLED",
"signed": true,
"activated": true,
"pdf_generated": true
},
"meta": {
"timestamp": "2025-01-15T10:30:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}{
"success": false,
"error": {
"code": "BAD_REQUEST",
"message": "Invalid request"
},
"meta": {
"timestamp": "2025-01-15T10:30:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}{
"success": false,
"error": {
"code": "UNAUTHORIZED",
"message": "Authentication is required to access this resource"
},
"meta": {
"timestamp": "2025-01-15T10:30:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}{
"success": false,
"error": {
"code": "FORBIDDEN",
"message": "You do not have permission to access this resource"
},
"meta": {
"timestamp": "2025-01-15T10:30:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}{
"success": false,
"error": {
"code": "VALIDATION_ERROR",
"message": "Validation error",
"details": {
"field_name": "Field is required"
}
},
"meta": {
"timestamp": "2025-01-15T10:30:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}{
"success": false,
"error": {
"code": "INTERNAL_ERROR",
"message": "Internal server error"
},
"meta": {
"timestamp": "2025-01-15T10:30:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}{
"success": false,
"error": {
"code": "UNSUPPORTED_MEDIA_TYPE",
"message": "Unsupported media type: text/plain. Supported: application/json"
},
"meta": {
"timestamp": "2025-01-15T10:30:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}Get VeriFactu configuration GET
**Deprecated.** Use `GET /v1/companies/{company_id}/verifactu-configuration`, which behaves identically. Returns the VeriFactu configuration in force for the company (NIF) in focus. - **Writable state:** `enabled` says whether VeriFactu is on, `apply_by_default` whether it is applied by default to new invoices. - **Resolved state:** `status`, `signed`, `activated` and `nif_status` are read-only and resolved server-side.
Update user preferred language PUT
**Deprecated — use `PATCH /v1/me` instead.** The preferred language belongs to the person, not to a company's configuration. Updates the authenticated user's preferred language. - **What it affects:** the language of the emails BeeL sends to the user and of the translated labels the API returns, such as the invoice template names in `GET /v1/invoice-customization-options`. - **Supported languages:** `es` (Spanish), `en` (English) and `ca` (Catalan).