The Taad API
Your recordings, transcripts, notes, to-dos and calendar, from your own code.
The Taad API lets your own code do what you do in Taad: read your recordings, their transcripts and notes, add and change to-dos and calendar events, search everything you've recorded, send audio to be transcribed and written up, and ask questions across your meetings. Webhooks tell your systems the moment something changes, so nothing has to keep asking.
It's built for scripts, CRMs and ERPs, and tools like Zapier, Make and n8n. If you'd rather talk to your meetings from Claude or ChatGPT, use the MCP connector instead: no key to copy.
Start in three steps
Make a key
Open Settings › Developers in Taad and choose Make a key. Tell it what the key is for and it picks what the key may do. Copy the key: it's shown once.
The API is for people and teams who pay for Taad: a paid plan, or money in your API wallet. See Paying for the API.
Check it works
curl https://api.taad.app/v1/me \
-H "Authorization: Bearer $TAAD_API_KEY"You get back what the key is: its name, where it reaches and what it may do.
Read your recordings
curl "https://api.taad.app/v1/recordings?created_after=2026-10-01&limit=10" \
-H "Authorization: Bearer $TAAD_API_KEY"Then open one with its transcript and notes: GET /v1/recordings/{id}, GET /v1/recordings/{id}/transcript, GET /v1/recordings/{id}/notes.
What it can do
The basics
- One address:
https://api.taad.app/v1. JSON in and out, names insnake_case, times in UTC. - Your key goes in a header,
Authorization: Bearer taad_…, from your server. Never in a URL, never in a web page: the API refuses calls from browsers. - Reading and changing your data is free. Sending audio, asking questions and rewriting notes cost a little, from your plan's minutes or your API wallet.
- Every answer carries a request id (
Taad-Request-Id). Quote it if you write to us. - The full reference is under Reference in the sidebar, and the same description as an OpenAPI file at /openapi.json, for generating a client.