Archivar un bloque
Block catalogue
DELETE /v1/blocks/{id}
Archive a block. Nothing is destroyed, and assistants that reference it keep using it.
DELETE
Archivar un bloque
Archives the block. Despite the verb, nothing is deleted: the block, its whole version history and every assistant reference to it survive. It is the same write as
PATCHing is_archived: true, and it is undone the same way.
Endpoint
Required scope
assistants:write
Headers
Path parameters
Example request
Response
204 No Content
Archived. No body.401 Unauthorized
Missing, invalid, revoked, or expired token.403 Forbidden
The token does not have theassistants:write scope.
404 Not Found
No block with that id in the token’s company and project.502 Bad Gateway
The assistant service is unreachable.Operational notes
- Retiring a block is two calls. Detach it from each assistant, then archive it. Archiving alone changes nothing about what the assistants say.
- Archiving an already-archived block succeeds, so a retry is safe.
- Undo with
PATCHandis_archived: false. There is no separate unarchive endpoint. - There is no hard delete in this API. Neither blocks nor versions can be destroyed through the public surface; the worst you can do is archive.
- Archived blocks are still readable by id with
GET /v1/blocks/{id}and appear in the catalogue when you passinclude_archived=true.