List first-class thread runs
GET
/v1/threads/{threadId}/runsReturn durable Thread v2 runs and their observer projections, with inferred read-only runs for legacy threads when no durable run exists.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| threadId | path | string | Yes | Thread ID |
Query parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| status | query | string | No | — |
| kind | query | string | No | — |
| limit | query | integer | No | — |
| order | query | asc | desc | No | Runs default to newest first; set asc for chronological order. |
| offset | query | integer | No | — |
| includeLegacy | query | boolean | No | — |
Body schema
This endpoint does not require a request body.
None.
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Thread run listapplication/json
None.