List Run Events

GET /runs/{run_id}/events

?after_seq= is the replay cursor. The journal is authoritative; the live stream is an accelerator over it (I-25).

?type= filters server-side and repeats for a set (?type=delta&type=notice). Annex 16 §3.3 specifies the Events tab as filterable by type, and filtering a fetched page in the browser hides every match that fell outside it (D-571, D-628). An unknown value is a 422 from the enum rather than a silently empty page.

Role floor

Requires viewer or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Parameters

Name	In	Type		Notes
run_id	path	string (uuid)	required	—
after_seq	query	integer	optional	Default 0. min 0
limit	query	integer	optional	Default 500. min 1 max 1000
type	query	run.start | run.status | run.end | segment.start | segment.end | text.delta | thinking.delta | tool.call | tool.result | suspend | resume | notice | error[] | null	optional	—

Responses

Status	Description	Body
200	Successful Response	Page_RunEventView_
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

curl -X GET https://your-deployment.example.com/runs/{run_id}/events \
  -H "Authorization: Bearer $COBRE_TOKEN"

Response — Page_RunEventView_

Field	Type		Notes
items	RunEventView[]	required	—
next_cursor	string | null	optional	—
total	integer | null	optional	—