List resource files
GET
/v1/servers/{serverId}/filesList files and directories in a resource workspace.
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 |
|---|---|---|---|---|
| serverId | path | string | Yes | Resource ID |
Query parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| path | query | string | No | Relative folder path to list |
| depth | query | integer | No | Recursion depth. Use `1` for immediate children only. |
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 listapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| serverId | string | No | Resource ID. |
| path | string | No | Workspace-relative file path. |
| depth | integer | No | — |
| files | object[] | No | — |
| files[].path | string | No | Workspace-relative file path. |
| files[].size | integer | No | — |
| files[].lastModified | string | No | — |
| files[].type | file | directory | No | — |
| files[].hasChildren | boolean | No | — |
| count | integer | No | — |