List orchestrations

GET/v1/orchestrations

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
environmentIdquerystringNo—
statusquerydraft | active | archivedNo—
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.

200Orchestration listapplication/json
FieldTypeRequiredDescription
objectstringNo—
dataobject[]No—
data[].idstringNoUnique identifier.
data[].userIdstringNoUser ID.
data[].namestringNoHuman-readable name.
data[].environmentIdstringNoComputer ID.
data[].strategyparallel | sequential | conditional | map_reduceNo—
data[].coordinatorAgentIdstringNo—
data[].stepsobject[]No—
data[].steps[].idstringNoUnique identifier.
data[].steps[].agentIdstringNoAgent ID.
data[].steps[].namestringNoHuman-readable name.
data[].steps[].instructionsstringNo—
data[].steps[].inputsobjectNo—
data[].steps[].dependsOnstring[]No—
data[].steps[].conditionstringNo—
data[].statusdraft | active | archivedNoCurrent lifecycle status.
data[].createdAtstringNoISO 8601 timestamp.
data[].updatedAtstringNoISO 8601 timestamp.
has_morebooleanNo—
total_countintegerNo—
List orchestrations
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow