Delete a contact
Delete a contact.
- It is a soft delete: the contact disappears from every read surface — list, search, options and selectors, stats, export, activities and its own detail, which answers 404
contact_not_foundfrom then on — while nothing is physically removed. - Its identity, roles, directional profiles, bank accounts, legacy aliases and every invoice, quote, delivery note or purchase invoice that references it are preserved exactly as they were, and those documents keep showing their customer or supplier data.
- Deleting releases the fiscal identity and the
external_id, so the same tax ID or external ID can be registered again as a different contact. - A deleted contact can no longer be used in new documents, not even through its legacy alias.
- The operation is irreversible through the API —
PUT /contacts/{contact}/restoreonly unarchives — and deleting an unknown, foreign or already deleted UUID returns 404contact_not_found. - For a reversible removal that keeps the contact readable, use
POST /contacts/{contact}/archiveinstead. - It emits the
contact.deletedwebhook event.
In: header
Path Parameters
Headers
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 409 idempotency_key_reused. 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.
1 <= length <= 255Pin 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.
dateOperate on behalf of a child company (gestoría master key): pass its public id (UUID v7) and the request runs against that child's data without changing the key's scope, tier or environment (omit to use the key's own company). Invalid UUID → 400 parameter_invalid_uuid; unknown or non-owned id → 404 profile_not_found. See the Acting on behalf guide.
uuidResponse Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json