Transcript results
Retrieve a predictable JSON result with job status, full text, media duration, and timestamped segments.
A result shape designed for downstream applications
Use full text for search, summaries, and indexing. Use segments for time-aware interfaces, citations, subtitles, and navigation back to the original recording.
Full transcript text
Completed jobs return normalized text in data.text.
Timestamped segments
Segment start and end offsets support synchronized interfaces.
Explicit status
processing, completed, and failed states keep polling logic deterministic.
Failure details
Failed jobs place a processing message in data.error; map or sanitize it before end-user display.
From request to transcript
A predictable sequence you can reuse in server applications, automations, and internal tools.
- 01
Persist the job ID
Store data.id from the create response with your own domain record.
- 02
Poll with backoff
GET the job-specific endpoint without creating duplicate work.
- 03
Process once
On completed, save text and segments; on failed, log data.error, show your own mapped message, and stop.
Make the request
Examples use the production API origin and an environment variable for the secret key.
curl https://fast-transcriber.com/api/v1/transcriptions/95c3fdd8-1234-4abc-9def-0123456789ab \
--header "Authorization: Bearer $FAST_TRANSCRIBER_API_TOKEN"Requirements and boundaries
- Only the get-one endpoint includes completed text and segments.
- List responses intentionally keep text and segments null.
- A job ID is visible only to the account that created it.
- Do not keep polling completed or failed jobs.
Frequently asked questions
When does text become available?+
data.text is populated only when status is completed.
Does the REST API return DOCX, SRT, or PDF?+
The current public API returns JSON text and segments. File-export endpoints are not part of v1.
How do I identify speakers?+
Create the job with Pro speaker diarization enabled. A segment can then include a speaker value when available.