List voice sessions

GET/v1/voice-agents/sessions

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
agentIdquerystringNo—
threadIdquerystringNo—
channelqueryweb | phoneNo—
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.

200Voice sessionsapplication/json
FieldTypeRequiredDescription
objectstringNo—
voiceSessionsobject[]No—
voiceSessions[].idstringNoUnique identifier.
voiceSessions[].agentIdstringNoAgent ID.
voiceSessions[].threadIdstringNoThread ID.
voiceSessions[].bindingIdstringNo—
voiceSessions[].providerxaiNo—
voiceSessions[].channelweb | phoneNo—
voiceSessions[].statusinitializing | active | completed | failed | cancelledNoCurrent lifecycle status.
voiceSessions[].xaiCallIdstringNo—
voiceSessions[].xaiSessionIdstringNo—
voiceSessions[].fromNumberstringNo—
voiceSessions[].toNumberstringNo—
voiceSessions[].startedAtstringNoISO 8601 timestamp.
voiceSessions[].endedAtstringNo—
voiceSessions[].durationSecondsnumberNo—
voiceSessions[].metadataobjectNoFree-form metadata object.
countintegerNo—
List voice sessions
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow