Update workspace binding

PATCH/v1/workspace-bindings/{bindingId}

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
Query parameters
None.

Body schema

Content type: application/json · Optional

FieldTypeRequiredDescription
projectIdstringNoProject ID.
namestringNoHuman-readable name.
localPathstringNo
syncRootstringNo
ignorePatternsstring[]No
syncModeoff | manual | watchNo
executionModelegacy_remote | bridge_localNo
lastPushedSnapshotIdstringNo
lastPulledSnapshotIdstringNo

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Workspace binding updatedapplication/json
FieldTypeRequiredDescription
bindingobjectNo
binding.idstringNoUnique identifier.
binding.userIdstringNoUser ID.
binding.deviceIdstringNo
binding.environmentIdstringNoComputer ID.
binding.projectIdstringNoProject ID.
binding.namestringNoHuman-readable name.
binding.localPathstringNo
binding.syncRootstringNo
binding.ignorePatternsstring[]No
binding.syncModeoff | manual | watchNo
binding.executionModelegacy_remote | bridge_localNo
binding.lastPushedSnapshotIdstringNo
binding.lastPulledSnapshotIdstringNo
binding.createdAtstringNoISO 8601 timestamp.
binding.updatedAtstringNoISO 8601 timestamp.
404Resource not foundapplication/json
FieldTypeRequiredDescription
errorstringNo
Update workspace binding
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow