Listar los bloques de un asistente
Assistant blocks
GET /v1/assistants/{id}/blocks
List the blocks wired into one assistant, in prompt order, with metadata and no content.
GET
Listar los bloques de un asistente
The middle step of the drill-down: which assistants exist → which blocks make up this one → what 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 theassistants: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
blocksarray on the assistant. Checkis_archivedif you want to surface it in a UI. content_writabletells you whether you may edit it before you try. It isfalseforproduct_info,store_info,reservation_info,tables_infoandtags, which only the portal can save.familyis derived fromtype, 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, andtotalis the real count. - A reference to a block that no longer exists is dropped silently. If the list is shorter than the
blocksarray on the assistant, a referenced block was hard-deleted out of band; clean it up withPUT /v1/assistants/{id}/blocks.