Get file history inside a thread
GET
/v1/threads/{threadId}/files/historyList step-level history entries for a single file path inside a thread.
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 |
|---|---|---|---|---|
| path | query | string | Yes | — |
| limit | query | integer | No | — |
| offset | query | integer | 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.
200File history entriesapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| object | string | No | — |
| threadId | string | No | Thread ID. |
| path | string | No | Workspace-relative file path. |
| data | object[] | No | — |
| data[].threadId | string | No | Thread ID. |
| data[].path | string | No | Workspace-relative file path. |
| data[].changedPath | string | No | — |
| data[].stepId | string | No | Step ID. |
| data[].sequence | integer | No | — |
| data[].title | string | No | Display title. |
| data[].eventType | string | No | — |
| data[].snapshotBeforeId | string | No | — |
| data[].snapshotAfterId | string | No | — |
| data[].changeKind | string | No | — |
| data[].createdAt | string | No | ISO 8601 timestamp. |
| total_count | integer | No | — |
| has_more | boolean | No | — |