Skip to main content
DELETE
Eliminar un asistente
Deletes the assistant. This is a hard delete of the assistant document and it cannot be undone. It is not a cascade. Every block the assistant referenced stays in the project catalogue, un-archived, with its full version history. Deleting an assistant unwires it; it does not clean up after it.
If your goal is to stop an assistant answering, PATCH it with is_active: false instead. That is reversible and keeps the configuration intact.

Endpoint

Required scope

assistants:write

Headers

Path parameters

Example request

Response

204 No Content

Deleted. No body.

401 Unauthorized

Missing, invalid, revoked, or expired token.

403 Forbidden

The token does not have the assistants:write scope.

404 Not Found

No assistant with that id in the token’s company and project. A repeated delete lands here, so treat 404 as “already gone” when retrying.

502 Bad Gateway

The assistant service is unreachable.

Operational notes

  • The blocks are orphaned, not deleted. They remain in the catalogue with no assistant referencing them. If they were only ever used by this assistant, archive them afterwards or they accumulate.
  • Knowledge documents are untouched. Deleting an assistant removes its assignments, not the documents themselves.
  • Anything still routing to this assistant will stop working. The delete does not check for inbound routes, channels or funnel stages pointing at it. Repoint them first.
  • A retry is safe. The operation is idempotent from the caller’s point of view: the second call is a 404, never a partial delete.

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 - undefined