Skip to main content
GET

Path Parameters

string
required
The agent ID to retrieve call logs for (UUID format)

Query Parameters

integer
default:"1"
Page number for pagination (1-indexed)
integer
default:"50"
Number of items per page (max 100)

Call Log Object

Core Fields

Transcript Data

transcript_json entry structure:
System entries are logged for events like call transfers, webhook executions, and call end reasons.

What the timestamps mean

All times are Unix epoch seconds (UTC).
speech_started_at, speech_ended_at, transcript_final_at and latency are present on calls made after the reply-timing release, and only where the platform could measure them.

Reply timing

Agent lines carry a latency object with that reply’s timing, in milliseconds. Every field is optional — a value is only present when the platform measured it. The caller-side fields (end_of_turn_ms, transcription_ms, turn_hook_ms) stay with the turn until an agent line carries the caller’s wait, so a message a tool speaks for itself does not take them from the reply. Tool time is always its own step, never part of the AI time, and a tool that did not run (an unknown tool name, or a rejected call) reports no duration.
Agents that use a single speech-to-speech model — rather than separate speech-to-text, AI model and voice — report no caller wait (total_ms) and none of the model or voice steps, so they never appear in turnLatency. Their lines still carry speech times, interrupted, and any tool times.

Call Timing

Session Metadata

Tool-call entries carry tool_call.duration_ms: how long that tool ran, in milliseconds.

Recording

Recording URLs are pre-signed S3 URLs. They may expire after a period of time. Store recordings in your own storage if you need permanent access.

Sharing

To give someone outside Telzino a link to a call’s transcript, use Share Call Transcript with the log’s id.

Timestamps

AI Summary Format

The summary_text field contains an AI-generated summary in Markdown format: