Skip to content

Get outcomes

Recordings and transcripts

Fetch a finished call's transcript, a fresh signed recording URL and the post-call analysis.

On this page

Each row in a lead's calls[] carries three URLs: transcript_url, recording_url and analysis_url. They are Entrovox API paths that need your key, not public links, so no expiring URL ever sits in your logs. Fetch them once the call has ended. All three need only the read scope.

  1. Fetch the transcript

    GET /v1/calls/{id}/transcript returns the turns of the call.

    curl https://api.entrovox.com/v1/calls/call_01J8K3Q7M2/transcript \
      -H "Authorization: ApiKey $ENTROVOX_KEY"
    200OK
    {
      "data": {
        "call_id": "call_01J8K3Q7M2",
        "word_count": 412,
        "transcript": [
          { "speaker": "agent", "text": "Hi, this is Robin, an AI assistant…", "started_at": "2026-09-10T18:02:14Z", "duration_ms": 4200 },
          { "speaker": "customer", "text": "Yeah, I was looking at auto.", "started_at": "2026-09-10T18:02:19Z", "duration_ms": 1800 }
        ]
      }
    }

    speaker is agent (the AI), customer (the lead) or human_agent (your licensed agent after the transfer, when we have that audio).

  2. Get a fresh recording URL

    GET /v1/calls/{id}/recording-url returns a signed URL that is good for one hour. It covers the AI voice agent's session, and the audio after a transfer when we stored it.

    curl https://api.entrovox.com/v1/calls/call_01J8K3Q7M2/recording-url \
      -H "Authorization: ApiKey $ENTROVOX_KEY"
    200OK
    { "data": { "url": "https://storage.example.com/signed/recording.mp3?token=…", "expires_in": 3600 } }

    Three different answers can come back when there is no URL to return. Branch on error.code, not on the status alone:

    Statuserror.codeMeaningWhat to do
    404RECORDING_NOT_FOUNDThe call has no recording: it never connected, recording was off, or no recording is available. A failed upload can sometimes be recovered later, in which case it appears on the call object.Do not poll for it. Check the call object later if you need it.
    404RECORDING_NOT_READYThe call has a recording that is still being processed.Poll again after the Retry-After header (seconds). Partner subscriptions can also wait for call.recording.ready, once webhook delivery is live.
    503RECORDING_UNAVAILABLEThe recording exists but a link could not be made right now.Retry after Retry-After. Keep retrying with backoff.

    RECORDING_NOT_READY does not last forever. A recording that is still pending a few hours after the call ended is reported as RECORDING_NOT_FOUND. The full list is on the errors page.

  3. Get the analysis

    GET /v1/calls/{id}/analysis returns the post-call record. Prefer its call_outcome for analytics over the attempt-level disposition.

    curl https://api.entrovox.com/v1/calls/call_01J8K3Q7M2/analysis \
      -H "Authorization: ApiKey $ENTROVOX_KEY"

    The record includes call_outcome, outcome_confidence, outcome_reasoning, overall_sentiment, sentiment_score, dnc_detected, dnc_phrases, callback_detected, callback_datetime, wrong_number_detected, extracted_data, call_summary and follow_up_actions, plus timestamps.

When the media is ready

Hangup and analysis can arrive before the audio is uploaded, so a call can have a call_outcome while its recording is still pending. If the recording fetch answers RECORDING_NOT_READY, ask again after Retry-After. analysis_status on the call is pending, completed or failed.

Next steps

Back to the lead's status URL, or read how webhooks will tell you when media is ready.

Updated Nov 7, 2026