ANanam
Sessions

get session analytics

Changed on

Returns per-turn latency analytics for a session — where time was spent in the transcription → LLM → TTS → first-audio path for each conversational turn, plus session-level summary metrics. Analytics become available once the session has ended and the engine has delivered its session report; until then this endpoint returns 404. Analytics exist only for sessions where Anam runs the conversational pipeline (turnkey, custom LLM and ElevenLabs agent sessions) — LiveKit and audio-passthrough sessions never produce them. Message text is omitted unless includeMessages=true is passed and transcripts were enabled for the session. Anam-internal admin API keys may fetch analytics for sessions of any organization.

get/v1/sessions/{id}/analytics

Request

  • Base URL
    https://api.anam.ai
  • URL
    https://api.anam.ai/v1/sessions/{id}/analytics
  • Auth
    HTTP bearer

Path parameters

idstring uuid required

Session ID

Query parameters

includeMessagesboolean

When true, include the user/assistant message text on each turn. Only honoured when transcripts were enabled for the session and the session is not zero-data-retention; timing metrics are always returned.

Response

Successfully retrieved session analytics

sessionIdstring uuid
startTimestring date-time
endTimestring date-time nullable
durationSecondsnumber nullable
sessionType'turnkey' | 'custom_llm_server' | 'custom_llm_client' | 'livekit' | 'elevenlabs_agent' | 'null' nullable
exitStatusstring nullable
clientLabelstring nullable
clientMetadataobject nullable
personaIdstring uuid nullable
apiKeyIdstring uuid nullable

Changes