Get full call details
Returns comprehensive call information including:
- Basic call data
- Contact info (name, phone, email, company)
- Flow info (name, version)
- Transcript (structured messages with timestamps)
- AI Analysis (summary, sentiment, intents, topics, action items, outcome)
- Cost breakdown (LLM, TTS, STT, Telephony with details)
- Quality metrics (MOS, jitter, latency, packet loss)
- Timeline events
Authentication
Pass a JWT access token or an API key (prefixed with tif_live_) as a Bearer token.
Path parameters
Response
Call direction (inbound or outbound)
Whether AI-powered post-call analysis has been performed
User-facing computed call status
Total cost in USD (string for decimal precision)
Why a call ended — set once when a call reaches terminal state.
Unlike failure_code which categorizes technical failures, end_reason
captures the causal signal that ended the call regardless of success/failure.
First writer wins (COALESCE pattern in SQL).
Tracks the specific reason a call failed, enabling:
- Analytics (which failure types are most common)
- Callbacks (schedule callback for capacity-rejected inbound calls)
- Debugging (detailed failure tracking)
Human-readable failure description
AI-powered post-call analysis including summary, sentiment, intents, and action items
Call performance metrics — latency, conversation, and usage analytics
Recording lifecycle status: “started”, “ready”, or “failed”
Structured transcript of the conversation (ordered by timestamp)
Handoff case the AI passed when it transferred the call to a person:
reason, summary, optional caller_name, plus any custom fields
configured on the Transfer node. Present only for transferred calls.
Turn-by-turn conversation data with per-turn metrics and function calls
When voicemail detection produced a result (null if none)
Voicemail detection outcome (null if detection was off or no result): “voicemail_detected”, “human_detected”, or “undetermined”