A power dialer API that returns call transcripts

The three calls you need

All three take Authorization: Bearer ds_… from Settings → API Keys. Errors come back as { error } with a 400 for a bad parameter and a 401 for a bad or lapsed key.

What a call looks like

{
  "id": "a175…",
  "lead_id": "fdb4…",
  "status": "completed",
  "direction": "outbound",
  "duration_seconds": 214,
  "started_at": "2026-09-09T20:14:03Z",
  "recording_url": "https://api.twilio.com/…",
  "transcript": "Hi, is this Jane? … ",
  "ai_summary": "Jane runs a six-person accountancy practice …",
  "ai_disposition": "callback",
  "ai_next_steps": "Call back Thursday after 2pm with UK pricing.",
  "compliance_score": 80,
  "coaching_notes": "Skipped the reason-for-call line …",
  "disposition": "callback",
  "is_conversation": true,
  "has_transcript": true,
  "leads": { "id": "fdb4…", "name": "Jane Ellis", "company": "Ellis & Co", "phone": "+44…", "status": "callback" },
  "notes": [ { "outcome": "callback", "content": "Thursday pm", "created_at": "2026-09-09T20:18:40Z" } ]
}

Three fields are derived so you do not have to reconstruct them. disposition is the rep's own outcome if they logged one, else the AI's, else voicemail detection, else Twilio's status. is_conversation is true when there is a transcript, a human outcome, or a completed call over thirty seconds. has_transcript lets a list without transcripts (include_transcript=false, to keep a fifty-call page small) tell you which calls to fetch one by one.

Filtering by day, and the time zone rule

Every timestamp in the database is UTC, and every rep thinks in local days. date=today&tz=America/Denver resolves to the Denver day, daylight saving included, and the response echoes the window it used so you can check. Leave tz out and the day is the UTC day, which for a rep in Denver means the calls after 6 pm belong to tomorrow. That single omission is the cause of most “the recap is missing my evening calls” messages we get.

• since=2026-09-01&until=2026-09-07&tz=Europe/London is the first through the seventh, inclusive of the seventh, in London time. A date given as YYYY-MM-DD means the start of that local day for since and the end of it for until.
• since=2026-09-09T20:00:00Z is an instant and is used as written. Mixing an instant with a date is fine.
• has_transcript=true is the cheapest way to skip voicemails and no-answers; on a typical cold-calling day it drops the list from a hundred rows to the eight that matter.
• Pages are up to 200. A day rarely needs a second page; a month does, so walk page until the list comes back shorter than limit.

What Twilio alone gives you

If you already run on Twilio, its API will hand you every recording, and for $0.05/min of audio a transcription of it. What it will not tell you is who the call was to, what the rep marked it as, whether a task was promised, or what the point of the conversation was; a Twilio call is a SID, two numbers and a duration. DialSheet's transcript is produced inside Pro from the same recording, then joined to the lead and summarised, and the endpoint above is where the join comes out. The recording stays in your Twilio account and recording_url points at it, so nothing here locks the audio in.

The limits, stated

• A key sees one person’s data. Team-wide reading is the recap endpoint with scope=team, for organisation admins, and nothing else.
• No webhook on call completion yet. Poll with since; ai_status says whether the summary has run.
• AI fields exist only for recorded, answered calls, and they fill in a few minutes after the call ends.
• Pro only. A key created on Pro stops working the day the plan lapses, on the next request.
• No published rate limit; be reasonable, and page rather than asking for the whole year in one call.

Common questions