Caption lecture recordings for accessibility
Education teams with an accessibility obligation and a recording backlog. Captions are required, manual captioning is slow, and auto-captions from video platforms have no punctuation or speaker labels.
SRT and VTT per lecture from the same job that produced the transcript.
The flow
- TriggerThe lecture recording is published or lands in storage.
- SubmitOne job produces every format — you do not run it again per format.
- CollectPull result?format=srt and result?format=vtt from the same job id.
- AttachUpload the caption track alongside the video.
# submit — returns immediately, does not block curl -X POST https://whipscribe.com/api/v1/transcribe/url \ -H "X-API-Key: $KEY" \ -H "Idempotency-Key: lecture-recordings-to-captioned-lessons-$SOURCE_ID" \ -H "Content-Type: application/json" \ -d '{"url":"https://example.com/recording.mp4", "diarize":true, "word_timestamps":true}' → 202 {"job_id":"a1b2…","status":"queued"} # then poll — a self-serve (Pro) key collects by polling curl "https://whipscribe.com/api/v1/jobs/$JOB" -H "X-API-Key: $KEY" → {"status":"processing"} … {"status":"done"}
What it costs
A 12-week course of two-hour lectures is 24 hours — about $12 for the term. $8 per 1,000 minutes — about $0.48 an audio hour — and credits never expire.
Why this needs an API rather than a person
Compliance is per-item and continuous, which is exactly the shape a human should not be in.
Build it on
Your first transcript in the web app is free, any length, no card — that is how to check accuracy on your own audio before writing any code. The API itself has no free tier: a key is self-serve once your account has credit ($50 minimum, spendable on transcription, and it does not expire). $8 per 1,000 minutes — about $0.48 an audio hour — and credits never expire.
Transcribe a file free →Create an API keyAPI reference