Transcription API for sales and support teams
Every recorded call as searchable, speaker-labelled text with a summary — filed against the account automatically, so the CRM has what was actually said instead of what someone remembered to type.
- Step 1Zoom, Meet or phone recording completes
- Step 2POST /api/v1/transcribe/url · diarize
- Step 3Speaker-labelled transcript · summary · quotes
- Step 4Filed on the account in the CRM, searchable
From recording to business result: one POST, one poll, every output format from the same job.
Three things a sales & customer support business actually does with it
Each priced at the published rate — $8 per 1,000 minutes — about $0.48 an audio hour — as credits that never expire.
Zoom's recording.completed fires, the recording posts to the API, and the transcript plus a summary land on the account record. The pipeline review reads what the customer said.
A question asked on a call last month was answered on a call last month. Transcribe the queue and the support desk can search it, instead of re-solving it.
Pull the ten calls where a deal was won and the ten where it was lost. Summaries and quotes give the sales lead a coaching deck built from what actually happened.
What you can rely on — and what we are not
Record only with the consent your jurisdiction requires. The API does not check that for you; your call platform's consent prompt does.
Delete a call's audio and transcript from its page at any time. 30 days free, 365 paid, nothing used for training.
Customer audio is processed on our own GPUs and never forwarded to a third-party model.
The whole integration
Two calls. No SDK to learn, no model to host, no GPU to rent.
# submit — returns a job id immediately curl -X POST https://whipscribe.com/api/v1/transcribe/url \ -H "X-API-Key: $KEY" \ -H "Idempotency-Key: sales-and-support-$RECORDING_ID" \ -H "Content-Type: application/json" \ -d '{"url":"https://example.com/recording.mp3","diarize":true,"word_timestamps":true}' → 202 {"job_id":"a1b2…","status":"queued"} # poll, then collect — every format from the one job curl "https://whipscribe.com/api/v1/jobs/$JOB" -H "X-API-Key: $KEY" curl "https://whipscribe.com/api/v1/jobs/$JOB/result?format=docx" -H "X-API-Key: $KEY" curl "https://whipscribe.com/api/v1/jobs/$JOB/insights" -H "X-API-Key: $KEY" # summary · quotes · topics
Wire it into what you already use
What it replaces or sits beside
Vendors sales & customer support teams compare us with — each has a side-by-side page.
Try it on a real recording before you build anything
Drop a file from your own business. First transcript free at any length, no card — that is how to check accuracy on your audio before writing code.
Questions sales & customer support teams ask
Does it work with Zoom cloud recordings?
Yes. Zoom's recording.completed webhook gives you a download URL; fetch it with the event's download_token and submit it. The Zoom integration page has the exact shape, including the 3-second acknowledgement Zoom requires.
Can it tell the rep from the customer?
With diarize enabled, yes — each speaker is labelled. Map the labels to names in your own code once, and every transcript reads as rep and customer.
Will it work with our CRM?
Anything with an API or a Zapier/Make connector. The transcript and summary are JSON; where they land is your automation's choice.
What does transcription cost for a sales & customer support business?
$8 per 1,000 minutes — about $0.48 an audio hour — as credits that never expire. First transcript free at any length. There are no seats and no monthly minimum: a 3-hour recording is about $1.44, two hundred half-hour calls about $48, a thousand-hour archive about $480 once.
Is there a free tier on the API?
No. The API has no free tier — a key needs a positive balance ($50 minimum, spendable on transcription). The free part is the web app: your first transcript there is free at any length, which is how to check accuracy on your own audio before paying anything.
How do we get an API key?
Self-serve: sign in, add credit, create the key at /apis/keys. No email, no sales call. Up to 10 active keys per account; rotate and revoke yourself.
How do results come back?
Submit, store the job id, poll GET /api/v1/jobs/{id} until done, then pull txt, json, srt, vtt or docx from the same job. Self-serve keys collect by polling; signed webhooks are an Enterprise feature.
Where is our audio processed?
On GPUs we own, in a private, secured cloud. It is never forwarded to OpenAI or any third-party model, and never used for training.
How long is audio kept?
30 days on the free plan, 365 on paid, and any file can be deleted on demand from its page. Wire deletion into your own retention rule if you need it automatic.
Does it label who is speaking?
Yes, when you enable diarize at submit time. Each speaker change is labelled; map the labels to names in your own code once.
What languages does it handle?
99+ languages, auto-detected, or set explicitly. Set it when you know it — auto-detect on a short or noisy clip is the most common cause of a wrong-language transcript.
Can we automate it with tools we already use?
Yes — Zapier, Make, n8n, Airtable, Drive, Dropbox, S3, Zoom, Slack, Notion. Each integration page carries the platform's real step timeout and the submit-then-poll shape that survives it.
What about very long or very large recordings?
Files go up to several GB and are submitted whole, so timestamps stay coherent — nothing is chunked. Hand us a URL and let us fetch it rather than streaming it through a no-code platform.
Do we get a summary as well as the transcript?
Yes. GET /api/v1/jobs/{id}/insights returns a summary, key quotes, topics and speakers for the same job, at no extra charge.
Can we try it before building anything?
Yes — the widget on this page. Drop a real recording from your business; the first transcript is free at any length, no card, and you will know whether the accuracy is there before writing a line of code.
Demand behind this page — GSC 90d: 103 queries, 589 impressions, position 25.6 — 'sales call intelligence', 'calendar bot teams', 'how to compress a zoom recording to email'. Second-largest vertical by impressions and the closest to an API buyer.