List local execution sessions

GET/v1/threads/{threadId}/local-sessions

List additive local bridge execution sessions attached to a thread.

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
Query parameters
NameLocationTypeRequiredDescription
limitqueryintegerNo—
offsetqueryintegerNo—
statusquerycreated | running | completed | failed | cancelledNo—
deviceIdquerystringNo—

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.

200Local execution session listapplication/json
FieldTypeRequiredDescription
objectlistNo—
dataobject[]No—
data[].idstringNoUnique identifier.
data[].threadIdstringNoThread ID.
data[].userIdstringNoUser ID.
data[].organizationIdstringNo—
data[].createdByUserIdstringNo—
data[].deviceIdstringNo—
data[].workspaceBindingIdstringNo—
data[].environmentIdstringNoComputer ID.
data[].statuscreated | running | completed | failed | cancelledNoCurrent lifecycle status.
data[].metadataobjectNoFree-form metadata object.
data[].errorstringNo—
data[].startedAtstringNoISO 8601 timestamp.
data[].lastHeartbeatAtstringNo—
data[].completedAtstringNoISO 8601 timestamp.
data[].createdAtstringNoISO 8601 timestamp.
data[].updatedAtstringNoISO 8601 timestamp.
total_countintegerNo—
List local execution sessions
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow