Skip to main content
GET
Listar el historial de un bloque
Every content save appends an immutable version. This lists them, newest first, so you can find a version_id to inspect or restore. No payloads. A block edited a few hundred times would make this response megabytes, for a list whose only job is to let you pick an id.

Endpoint

Required scope

assistants:read

Headers

Path parameters

Query 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 block with that id in the token’s company and project.

502 Bad Gateway

The assistant service is unreachable.

Operational notes

  • There is no total. The upstream store exposes no count for versions, and returning the page length as if it were the size of the set would make a client stop paginating early. Page until has_more is false.
  • is_current marks the version the block points at, which is what an unpinned assistant renders. Exactly one version per block has it.
  • version_number is monotonic and never reused. A restore appends a new number rather than reviving the old one, so restoring version 2 onto a block at version 5 gives you version 6 with version 2’s content.
  • Versions are never deleted. Not by archiving the block, not by deleting the assistant, and there is no endpoint that removes one.
  • An assistant may render a version that is not current, if it was pinned. Compare against pinned_version_id from its block list.

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

Query Parameters

limit
number
default:50
Required range: 1 <= x <= 200
offset
number
default:0
Required range: x >= 0

Response

200 - application/json
limit
number
required
offset
number
required
has_more
boolean
required

Si hay al menos una pagina mas despues de esta.

data
object[]
required