Push repository branch
POST
/v1/environments/{environmentId}/git/pushHow 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 |
Query parameters
None.
Body schema
Content type: application/json · Optional
| Field | Type | Required | Description |
|---|---|---|---|
| path | string | No | Workspace-relative file path. |
| branch | string | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Branch pushedapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| success | boolean | No | Whether the request succeeded. |
| sha | string | No | — |
| branch | string | No | — |
| path | string | No | Workspace-relative file path. |
| message | string | No | Message text. |
| stagedFiles | string[] | No | — |
| unstagedFiles | string[] | No | — |