Get workspace push session

GET/v1/workspace-bindings/{bindingId}/push-sessions/{pushSessionId}

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
NameLocationTypeRequiredDescription
bindingIdpathstringYesWorkspace binding ID
pushSessionIdpathstringYesWorkspace push session ID
Query parameters
None.

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.

200Workspace push session detailsapplication/json
FieldTypeRequiredDescription
pushSessionobjectNo
pushSession.idstringNoUnique identifier.
pushSession.workspaceBindingIdstringNo
pushSession.userIdstringNoUser ID.
pushSession.deviceIdstringNo
pushSession.environmentIdstringNoComputer ID.
pushSession.projectIdstringNoProject ID.
pushSession.statusprepared | superseded | cancelledNoCurrent lifecycle status.
pushSession.planSignaturestringNo
pushSession.planobjectNo
pushSession.metadataobjectNoFree-form metadata object.
pushSession.createdAtstringNoISO 8601 timestamp.
pushSession.updatedAtstringNoISO 8601 timestamp.
404Resource not foundapplication/json
FieldTypeRequiredDescription
errorstringNo
Get workspace push session
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow