Get the additive thread timeline projection
GET
/v1/threads/{threadId}/timelineReturn canonical events together with run projections, deliveries, activity groups, and a bounded read-only compatibility projection of legacy messages, logs, and steps. No cursor returns the newest canonical page in chronological order; use before=olderCursor for history and after=streamCursor for newer committed events.
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 |
|---|---|---|---|---|
| after | query | integer | No | — |
| before | query | integer | No | — |
| cursor | query | integer | No | Backward-compatible alias for `before`. |
| limit | 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 timeline projectionapplication/json
None.
Get the additive thread timeline projection
Loading...
Response 200
Loading...