Skip to main content
DELETE
Eliminar un contacto
Deletes a contact along with its change history. The deletion is permanent — there is no soft-delete flag and no restore endpoint.
This is not reversible. If the person writes to your channel again, Keebai creates a brand new contact with a new _id, and any CRM ticket that pointed at the old one is left orphaned.

Endpoint

Required scope

contacts:delete This is a separate scope from contacts:write on purpose — an integration that syncs contact data should be able to create and update without being able to destroy.

Headers

Path parameters

Example request

Response

204 No Content

The contact was deleted. The response body is empty.

401 Unauthorized

Missing, invalid, revoked, or expired token.

403 Forbidden

The token does not have the contacts:delete scope.

404 Not Found

No contact with that id, or the contact belongs to a different company.

502 Bad Gateway

The messaging service could not complete the delete.

Operational notes

  • Conversations and messages survive. Only the contact record and its change history are removed; the message history stays in place, detached.
  • CRM records are not cascaded. Tickets and notes that reference this contact through chat_user keep pointing at an id that no longer resolves. Clean them up first with GET /v1/crm/tickets filtered by chat_user_id.
  • Deleting is rarely what you want. For a contact who asked to stop being messaged, updating a custom field your integration checks before sending is safer than destroying the record.

Authorizations

Authorization
string
header
required

Personal Access Token con prefijo kbai_pk_. Generar desde el portal con permiso developer.manage_tokens.

Path Parameters

id
string
required

Response

204

Contacto eliminado