Skip to main content
DELETE
Desadjuntar un bloque de un asistente
Removes one block from the assistant’s prompt. The block is untouched: it stays in the project catalogue with its full history, and any other assistant referencing it keeps using it. This is the counterpart to attaching. To get rid of the block itself, archive it as well.

Endpoint

Required scope

assistants:write

Headers

Path parameters

Example request

Response

200 OK

The full assistant, same shape as GET /v1/assistants/{id}, without the block.

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.

502 Bad Gateway

The assistant service is unreachable.

Operational notes

  • Detaching an identity block leaves the assistant without one. Nothing prevents removing the personification, and the assistant will keep answering with whatever identity remains, which may be none. Attach a replacement in the same flow.
  • Detaching does not archive and does not delete. The block stays in the catalogue. If it was only used here, archive it too or it lingers.
  • Detaching the same block twice returns the assistant unchanged, so a retry is safe.
  • This removes every reference to that block id, which matters if the block was attached twice by repeated attach calls.

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
blockId
string
required

Response

200 - application/json
assistant
object
required