VeriFactu

Update VeriFactu settings

Update your company's VeriFactu settings (mode, environment and, with remission_mode, who remits to AEAT).

  • A locked transition returns 422 business_rule_violation; once enabled, VeriFactu mode cannot be disabled.
  • A third-party remission_mode needs a current representation of its kind, else 422 subcode representation_required.
  • Every mode change is audited.
patch/companies/{company}/verifactu/settings

Request

  • Base URL: https://api.factuarea.com/v1
  • URL: https://api.factuarea.com/v1/companies/{company}/verifactu/settings
  • Auth: one of:
    • HTTP bearer
    • API key in header X-API-Key

Path parameters

companystring uuid required

Public identifier (UUID v7) of the company. Get it from GET /v1/me (data.scope[].id).

Headers

Idempotency-Keystring required
Example:01928f10-7c0e-7c4a-9b7d-2f8a6e3c1d4b

Client-generated opaque key (up to 255 characters; UUID v7 recommended) that makes retries safe: the first response is cached and replayed for repeats without re-executing the mutation. Reusing a key with a different body returns 422 idempotency_key_reused; the values of secret fields (password, secret…) count as part of the body, so retrying with a corrected secret under the same key is a different request, never the replay of the earlier answer. See the Idempotency guide. Required on this operation: repeating it delivers an effect that cannot be taken back (an email sent, a file generated, a third-party call, a charge), so a request without this header is rejected with 422 idempotency_key_required before any business logic runs.

Factuarea-Versionstring date
Example:2026-06-01

Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.

Request body

enabledboolean
mode'verifactu' | 'no_verifactu'
auto_transmitboolean
environment'sandbox' | 'production'
notification_emailsstring[]
remission_mode'own_certificate' | 'social_collaborator' | 'power_of_attorney'

Who submits the VeriFactu records of your company to AEAT. It does not change whether the company operates in VERIFACTU or NO VERIFACTU mode: it only decides whose electronic certificate signs and submits the records. own_certificate (default): the records are submitted with the electronic certificate of the company itself. social_collaborator: Factuarea submits the records on your behalf as a social collaborator, with the certificate of Factuarea; it needs an active social_collaboration_annex_i representation. power_of_attorney: Factuarea submits the records on your behalf as an attorney-in-fact, with the certificate of Factuarea; it needs an active aeat_power_of_attorney representation.

Response

Example response

{
  "data": {
    "object": "verifactu_config",
    "enabled": true,
    "mode": "verifactu",
    "auto_transmit": true,
    "environment": "production",
    "notification_emails": [
      "avisos@empresa.es"
    ],
    "is_locked_until": "2026-12-31T23:59:59+01:00",
    "has_active_certificate": true,
    "active_certificate_id": "01931b3e-7c4a-7f2e-9a8b-3c5d6e7f8a13",
    "updated_at": "2026-04-15T10:30:00+02:00",
    "remission_mode": "own_certificate",
    "presenter_certificate_status": "valid"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.