Get computer change file
GET
/v1/environments/{environmentId}/changes/{changeId}/fileRead one file from a historical computer change.
Use the default JSON response for text payloads. Set format=raw when you want the raw
historical bytes for previews or binary assets.
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 |
|---|---|---|---|---|
| environmentId | path | string | Yes | Environment ID |
| changeId | path | string | Yes | — |
Query parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| path | query | string | Yes | File path within the change |
| format | query | raw | No | Return the raw historical file bytes instead of a JSON content payload |
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.
200Change file contentapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| path | string | No | Workspace-relative file path. |
| snapshotId | string | No | Snapshot ID. |
| content | string | No | Raw text content. |