Enqueue local session control command

POST/v1/threads/{threadId}/local-sessions/{localSessionId}/control

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
threadIdpathstringYesThread ID
localSessionIdpathstringYesLocal execution session ID
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
commandTypecancel | pause | resume | messageYes
payloadobjectNo

What the API returns

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

201Local session control command createdapplication/json
FieldTypeRequiredDescription
commandobjectNo
command.idstringNoUnique identifier.
command.sessionIdstringNoSession ID.
command.threadIdstringNoThread ID.
command.userIdstringNoUser ID.
command.commandTypecancel | pause | resume | messageNo
command.payloadobjectNo
command.statuspending | acknowledged | completed | cancelledNoCurrent lifecycle status.
command.createdAtstringNoISO 8601 timestamp.
command.acknowledgedAtstringNo
command.completedAtstringNoISO 8601 timestamp.
command.updatedAtstringNoISO 8601 timestamp.
Enqueue local session control command
Loading...
Response 201
Loading...
See the ACP quickstart and SDK flow