Read the event cursor for a context

GET

/api/events/{kb_context_id}/cursor

Maintainer:Not configured

OperationId:cursor

The newest event id on the context among the events its change feed would serve you, or null. A hint that can miss a change, not a freshness proof. It is ordered by occurred_at, when the acting transaction began, so a long transaction that begins before a short one and commits after it never moves the cursor past the short one's event. To see every change, read the change feed (GET /api/events/{kb_context_id}/changes), which is commit-ordered and does not have this race.

Request

Authorization

JWT Bearer

Add the parameter

Authorization

to Headers

Example:

Authorization: ********************

Path Params

Header Params

Responses

🟢200OK

application/json

Latest event id for the context

Bodyapplication/json

🟠401Unauthorized

Request Example

Shell

JavaScript

Java

Swift

curl --location '/api/events//cursor' \
--header 'X-Temper-Surface;' \
--header 'Authorization: Bearer <token>'

Response Example

200 - Example 1

{
    "latest_event_id": "17d54501-120f-4f70-bb3e-02f002c58ecb"
}

Modified at 2026-11-12 18:30:59

Read a context's changes after a position

Read a node or edge's event trail