Complete local execution session

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

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 · Optional

FieldTypeRequiredDescription
statuscompleted | failed | cancelledNoCurrent lifecycle status.
completedAtstringNoISO 8601 timestamp.
errorstringNo
metadataobjectNoFree-form metadata object.

What the API returns

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

200Local execution session completedapplication/json
FieldTypeRequiredDescription
sessionobjectNo
session.idstringNoUnique identifier.
session.threadIdstringNoThread ID.
session.userIdstringNoUser ID.
session.deviceIdstringNo
session.workspaceBindingIdstringNo
session.environmentIdstringNoComputer ID.
session.statuscreated | running | completed | failed | cancelledNoCurrent lifecycle status.
session.metadataobjectNoFree-form metadata object.
session.errorstringNo
session.startedAtstringNoISO 8601 timestamp.
session.lastHeartbeatAtstringNo
session.completedAtstringNoISO 8601 timestamp.
session.createdAtstringNoISO 8601 timestamp.
session.updatedAtstringNoISO 8601 timestamp.
Complete local execution session
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow