/v1/audio/transcriptions.
Architecture
language, prompt, response_format) are forwarded to the deployment, and the response is returned as-is.
What you get out of the box
- OpenAI-compatible
/v1/audio/transcriptionsendpoint (multipart upload) response_format:json,text,srt,vtt(availability depends on the deployed model)- Per-second billing metered on transcribed audio duration
Speaker diarization and PII redaction are not built into the managed transcription endpoint. The response shape, including any segment or speaker fields, is determined by the ASR model you deploy. If you need diarization or redaction, run those steps on the deployment side or as a post-processing pass over the returned text.
Example prompt
In the dashboard:Quick example
Output shape
The defaultjson format returns the transcribed text:
text, srt, and vtt formats return the corresponding plain-text or subtitle body. Any additional fields depend on the ASR model you deploy, so check your deployment’s response before relying on a specific schema.