List workspace bindings

GET/v1/workspace-bindings

List local folder to environment bindings for the authenticated user.

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
None.
Query parameters
NameLocationTypeRequiredDescription
deviceIdquerystringNo—
environmentIdquerystringNo—
projectIdquerystringNoFilter to a specific project. Use `none` for bindings without a project.
limitqueryintegerNo—
offsetqueryintegerNo—

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 binding listapplication/json
FieldTypeRequiredDescription
objectstringNo—
dataobject[]No—
data[].idstringNoUnique identifier.
data[].userIdstringNoUser ID.
data[].organizationIdstringNo—
data[].createdByUserIdstringNo—
data[].deviceIdstringNo—
data[].environmentIdstringNoComputer ID.
data[].projectIdstringNoProject ID.
data[].namestringNoHuman-readable name.
data[].localPathstringNo—
data[].syncRootstringNo—
data[].ignorePatternsstring[]No—
data[].syncModeoff | manual | watchNo—
data[].executionModelegacy_remote | bridge_localNo—
data[].lastPushedSnapshotIdstringNo—
data[].lastPulledSnapshotIdstringNo—
data[].createdAtstringNoISO 8601 timestamp.
data[].updatedAtstringNoISO 8601 timestamp.
total_countintegerNo—
List workspace bindings
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow