List files at a thread step
GET
/v1/threads/{threadId}/steps/{stepId}/filesList files and directories from the snapshot attached to a specific thread step.
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 |
| stepId | path | string | Yes | Thread step ID |
Query parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| prefix | query | string | 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.
200Step snapshot file listapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| object | string | No | — |
| threadId | string | No | Thread ID. |
| stepId | string | No | Step ID. |
| snapshotId | string | No | Snapshot ID. |
| prefix | string | No | — |
| data | object[] | No | — |
| data[].path | string | No | Workspace-relative file path. |
| data[].size | integer | No | — |
| data[].lastModified | string | No | — |
| data[].type | file | directory | No | — |
| data[].hasChildren | boolean | No | — |