Endpoint reference

Inspect persisted voice sessions.

Use this endpoint to review transcripts, tool calls, model and voice context, QA state, tags, summaries, and launch-governance evidence.

Endpoint contract

PropertyValue
MethodGET
Path/api/v1/voice-sessions
AuthenticationAuthorization: Bearer ${STATESET_VOICE_API_KEY}
Primary useInspect persisted conversation state, transcript artifacts, function calls, tags, and QA metadata.

Query parameters

ParameterDescription
limitMaximum session records to return.
offsetOffset for paginated review and export jobs.
statusFilter active, completed, failed, or reviewed session states where available.
stream_idUse when reconciling a realtime media stream to a persisted session.
agent_keyUse for prompt, tool, and rollout analysis by agent.

Example request

curl -sS "https://voice.stateset.app/api/v1/voice-sessions?limit=25&offset=0" \
  -H "Authorization: Bearer ${STATESET_VOICE_API_KEY}"

Response fields

FieldUse
stream_idJoin realtime media stream events to the persisted session.
call_sidJoin the session to Twilio call state and call logs.
transcriptReview what the caller and agent said for QA and prompt iteration.
function_callsInspect tools used by the agent, arguments, results, and failures.
summaryDisplay concise operational context in CRM, ticketing, or callback queues.
tagsDrive routing, review workflows, analytics, and launch-governance filters.

QA workflow

  1. Start from call logs or webhook events, then open the matching voice session.
  2. Review transcript turns, model output, tool calls, and escalation decisions.
  3. Record evaluation notes and tags for launch governance and prompt regression tracking.
  4. Feed recurring failure patterns into the agent contract, tool boundaries, and production readiness checklist.

Data governance

  • Limit access to transcript and tool-call data to teams that need operational review.
  • Use tenant-scoped API keys and separate admin credentials from runtime readers.
  • Define retention, redaction, and export practices before routing regulated traffic.
  • Use tags and evaluations to support audit trails without overexposing raw conversation data.