Get connected runtime run events

GET/v1/servers/{serverId}/runtime/agent/runs/{resourceRunId}/events

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
serverIdpathstringYesResource ID
resourceRunIdpathstringYesAgent runtime run ID
Query parameters
None.

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.

200Connected runtime run with eventsapplication/json
FieldTypeRequiredDescription
serverIdstringNoResource ID.
agentRuntimeIdstringNo
runobjectNo
run.idstringNoUnique identifier.
run.serverIdstringNoResource ID.
run.threadIdstringNoThread ID.
run.titlestringNoDisplay title.
run.inputstringNo
run.outputstringNo
run.modesync | asyncNo
run.statusqueued | running | completed | failed | cancelledNoCurrent lifecycle status.
run.errorstringNo
run.metadataobjectNoFree-form metadata object.
run.createdAtstringNoISO 8601 timestamp.
run.completedAtstringNoISO 8601 timestamp.
run.sessionProtocolstringNo
run.threadBackedbooleanNo
run.threadStatusstringNo
run.threadTitlestringNo
threadobjectNo
eventsobject[]No
events[].idstringNoUnique identifier.
events[].rolestringNo
events[].contentstringNoRaw text content.
events[].logTypestringNo
events[].logLevelstringNo
events[].createdAtstringNoISO 8601 timestamp.
Get connected runtime run events
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow