POST /revisions/:id/data/query (Command: list_session_events)
Request Body
Response
Pagination. Pass the response
cursor back as the request cursor to fetch the next page; stop when cursor is
null. The cursor is opaque, so send it back verbatim. It resumes after the last row evaluated, and it keeps the
after or before that bounded the first page.
Evaluation budget. The filter runs on the server. A request keeps reading until it has limit matches, the range is
exhausted, or it has evaluated 10,000 rows. Only that budget can end a page short while cursor is still live, so a
page of fewer than limit events with a cursor is not the end: keep reading until cursor is null.
Following the stream. An event can commit after an event with a larger id. Read
Settle time before you follow the stream with after, and
Boundary ids to start at a timestamp.
A deleted session is still served by id while its stream lasts, with session null under include_session.
Errors
Example
See also
- Get Session Event reads one event by its id.
- List Execution Events reads an execution’s own log.
- Listeners act on the same stream as it grows.

