Skip to main content
GET
Listar los bloques de un asistente
The middle step of the drill-down: which assistants existwhich blocks make up this onewhat one of them says. Returns each block’s type, family and name, plus its order and pinned_version_id on this assistant, sorted by order. No content: a block document holds none, which is why reading it is a separate call.

Endpoint

Required scope

assistants:read

Headers

Path parameters

Example request

Response

200 OK

401 Unauthorized

Missing, invalid, revoked, or expired token.

403 Forbidden

The token does not have the assistants:read 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

  • Archived blocks are included, on purpose. A block that is attached and archived still renders into the assistant’s prompt — archiving hides it from the catalogue, it does not switch it off. Omitting them here would make this list disagree with the blocks array on the assistant. Check is_archived if you want to surface it in a UI.
  • content_writable tells you whether you may edit it before you try. It is false for product_info, store_info, reservation_info, tables_info and tags, which only the portal can save.
  • family is derived from type, and decides which section of the prompt the block lands in. It is never something you send.
  • This is not paginated, because an assistant holds at most 50 blocks. There is no limit, and total is the real count.
  • A reference to a block that no longer exists is dropped silently. If the list is shorter than the blocks array on the assistant, a referenced block was hard-deleted out of band; clean it up with PUT /v1/assistants/{id}/blocks.

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

200 - application/json
data
object[]
required
total
number
required