Leer el contenido de un bloque
Block content
GET /v1/blocks/{id}/content
Read the current content of a block, as plain text for free blocks or as a structured payload for catalogue ones.
GET
Leer el contenido de un bloque
The last step of the drill-down: assistants → their blocks → this block’s content.
Returns the content of whichever version the block currently points at, together with that version’s id and number.
A catalogue block, configured in the portal:
Endpoint
Required scope
assistants:read
Headers
Path parameters
Example request
Response
200 OK
A free block, which is anything written through this API:401 Unauthorized
Missing, invalid, revoked, or expired token.403 Forbidden
The token does not have theassistants:read scope.
404 Not Found
No block with that id in the token’s company and project, orerror.code is BLOCK_CONTENT_NOT_FOUND because the block has never been saved and has no current version.
502 Bad Gateway
The assistant service is unreachable.Operational notes
edit_modetells you which field to read.freegives youcontentas text and nopayload;assistedgives youpayloadas an object and nocontent. Every block written through this API isfree.- The
payloadof an assisted block is an opaque object whose shape depends on the block type. It is returned as stored so you can inspect it, but it is not writable here — saving those types returns409. - Rich formatting authored in the portal flattens to text. Bold, italics, colours and inline function chips do not survive the round trip: you get the words, not the styling. If a block was carefully styled in the portal, prefer editing it there.
- This reads the block’s current version, which is not necessarily what a given assistant sees. An assistant with a
pinned_version_idrenders that version instead; read it withGET /v1/blocks/{id}/versions/{versionId}. created_byis never returned. It is an internal user id.