Runs
List a run's structural timeline
List a run’s structural timeline. Requires permission runs:read.
GET
List a run's structural timeline
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.
v2 compatibility notes
Milestones only
The structural timeline is the run’s milestones. Tool calls, model messages, error payloads and cost amounts are not returned; useGET /api/v2/runs/get for status and outputs and GET /api/v2/cost/summary for cost.
Each item is one milestone, oldest first by sequence: a checkpoint, handoff_initiated, handoff_completed, guardrail_tripped, intervention, cost_milestone, error or completion, with its timestamp and, when the runtime recorded them, durationMs, traceId and spanId (otherwise null). An item never names the agent, the tool, the runtime provider or a token or cost amount.
Visibility and paging
You needruns:read at the run’s home (its own org unit, else its workflow’s owning org unit) and at every company it carries, the same rule as GET /api/v2/runs/get. Any other run, and a run with neither home, answers 404 like a missing one.
limit is 1 to 100 (default 25; a larger value is 400 too_big). A page may be shorter than limit while meta.hasMore is true; follow meta.nextCursor as cursor until hasMore is false. A cursor the server cannot read answers 400. A running run’s timeline grows; the last page ends with meta.nextCursor: null, so read again from the start (without cursor) to pick up later milestones, and use sequence to skip the ones you already have.Authorizations
Response
One page of the run's milestones

