Skip to main content
GET
Historial de una seccion
Every text that section has held. A version is written on each save that changes the text, so saving without editing does not pad the history, and the newest version is what the agent is reading right now.

Endpoint

Required scope

agents:read

Path parameters

Query parameters

Example request

Response

200 OK

404 Not Found

No agent with that id in the token’s company and project.

Operational notes

  • The first item is the current text. There is no is_current flag because there is nothing to disagree with: the highest version_number is what the agent reads.
  • version_number is per section, not per agent. Two sections both have a version 1.
  • created_by is who saved it — a portal user’s email, the PAT owner’s email when it came through this API, or null for versions written before the field existed.
  • restored_from names the version this one copied, when it was born from a restore. It is how you tell an edit from a rollback.
  • An agent created before section history existed starts at version 1 with whatever text it had at that moment, not with its real past.

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
section
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