Elevenlabs Scribe V3 API Documentation

Elevenlabs Scribe V3 API Documentation

Playground

Try it on WaveSpeedAI!

ElevenLabs Scribe V3 Speech-to-Text transcribes recorded audio with automatic language detection, speaker labels, word-level timestamps, number formatting, and multilingual language hints for transcription, subtitles, captions, and meetings. Ready-to-use REST inference API, best performance, no coldstarts, affordable pricing.

Features

ElevenLabs Scribe V3 transcribes audio into structured text with automatic language detection, optional speaker diarization, word-level timestamps, audio-event tagging, number formatting, and language hints for multilingual recordings.

Use optional keyterms to provide recognition hints for names, technical terms, brands, or other vocabulary that may be difficult to recognize from audio alone.


Why Choose This?

  • Speech-to-text transcription — Convert recorded speech into structured transcript data.
  • Automatic language detection — Let the model detect the spoken language automatically, or provide a language code when known.
  • Speaker diarization — Enable diarize to label different speakers in multi-speaker recordings.
  • Word-level timestamps — Receive timing information for individual words for subtitle, editing, alignment, and search workflows.
  • Audio-event tagging — Include detected non-speech events such as laughter when tag_audio_events is enabled.
  • Keyterm guidance — Provide up to 100 recognition hints for names, brands, technical vocabulary, or domain-specific terms.
  • Number formatting — Choose whether numbers are written as digits or words.
  • Multilingual language hints — Provide additional language codes for recordings containing more than one language.

Parameters

ParameterRequiredDescription
audioYesAudio input provided by upload or public direct file URL.
language_codeNoISO-639-1 or ISO-639-3 language code. Omit for automatic language detection.
secondary_language_codesNoUp to 100 additional ISO-639-1 or ISO-639-3 language codes expected alongside the main language. Omit when not needed.
numbers_formatNoWrite numbers as digits (42) or words (forty-two). Omit to use the model default.
diarizeNoIdentify and label different speakers in the recording. Default: false.
tag_audio_eventsNoInclude detected audio events such as laughter in the transcription result. Default: true.
keytermsNoRecognition hints for important vocabulary. Supports up to 100 items; each term must be under 50 characters and contain at most 5 words. Additional pricing applies when any keyterms are provided.

How to Use

  1. Provide the audio — Upload a recording or supply a direct public audio-file URL.
  2. Set language optional — Provide language_code when the spoken language is known, or omit it for automatic detection.
  3. Enable diarization optional — Turn on diarize when speaker labels are needed.
  4. Configure audio events optional — Keep tag_audio_events enabled when non-speech events should be included.
  5. Add keyterms optional — Supply names, brands, technical vocabulary, or other recognition hints when needed.
  6. Set multilingual hints and number formatting optional — Add secondary_language_codes and choose numbers_format when needed.
  7. Submit — Process the recording and retrieve the transcript result.

Pricing

Pricing is based on the processed input audio duration.

ConfigurationPrice per Input Minute
Standard transcription$0.01
With one or more keyterms$0.012

Each request has a minimum billable duration of 10 seconds. Audio longer than 10 seconds is charged proportionally to its duration rather than rounded up to full minutes.

Example Costs

Audio DurationStandardWith Keyterms
30s$0.005$0.006
1 min$0.01$0.012
10 min$0.10$0.12
30 min$0.30$0.36
60 min$0.60$0.72

Only the first 60 minutes of input audio are processed and billed.

Providing one or more keyterms applies a 1.2× multiplier to the transcription price. The number of keyterms does not add separate per-item charges.


Best Use Cases

  • Interviews — Transcribe conversations with optional speaker labels.
  • Meetings — Create transcripts with speaker labels and word timing.
  • Podcasts — Convert spoken episodes into text for publishing, indexing, or subtitle workflows.
  • Subtitle preparation — Use word-level timestamps in caption and subtitle workflows.
  • Technical recordings — Use keyterms to provide recognition hints for specialized terminology.
  • Content search and indexing — Convert audio archives into structured text for downstream processing.

Pro Tips

  • Enable diarize when multiple people speak in the same recording.
  • Provide language_code when the spoken language is already known.
  • Use keyterms for uncommon names, brands, acronyms, product names, or technical vocabulary.
  • Keep keyterms short and specific instead of using full explanatory sentences.
  • Clear speech and low background noise are recommended.
  • Supply a direct audio-file URL rather than a webpage containing an embedded audio player.

Notes

  • Each request is billed for at least 10 seconds. This billing minimum does not extend or repeat the input audio.
  • Only the first 60 minutes of input audio are processed and billed.
  • keyterms supports up to 100 items.
  • Each keyterm must be under 50 characters and contain no more than 5 words. It cannot include <, >, {, }, [, ], or a backslash.
  • Keyterms provide recognition guidance but do not guarantee exact spelling.
  • Public URLs must point directly to an accessible audio file.

Authentication

For authentication details, please refer to the Authentication Guide.

API Endpoints

Submit Task & Query Result

set -euo pipefail

export WAVESPEED_API_KEY="your-api-key"

REQUEST_BODY=$(cat <<'JSON'
{
  "audio": "https://interactive-examples.mdn.mozilla.net/media/cc0-audio/t-rex-roar.mp3",
  "numbers_format": "digits",
  "diarize": false,
  "tag_audio_events": true,
  "keyterms": []
}
JSON
)

# 1. Submit the prediction once. Never retry this request automatically:
# a retry after an unclear failure can create a second, billed task.
CHECK='The task may already exist. Check History or the predictions list before submitting again.'
if ! SUBMIT_RESPONSE=$(curl --silent --show-error --fail-with-body \
  --connect-timeout 10 --max-time 60 \
  -X POST "https://api.wavespeed.ai/api/v3/elevenlabs/scribe-v3" \
  -H "Authorization: Bearer ${WAVESPEED_API_KEY}" \
  -H "Content-Type: application/json" \
  -d "${REQUEST_BODY}"); then
  printf 'Submit failed. %s\n' "${CHECK}" >&2
  exit 1
fi

TASK=$(printf '%s' "${SUBMIT_RESPONSE}" | jq 'if type == "object" and has("data") then .data else . end')
PREDICTION_ID=$(printf '%s' "${TASK}" | jq -r '.id // empty')
if [ -z "${PREDICTION_ID}" ]; then
  printf 'Submission response did not contain a prediction id. %s\n' "${CHECK}" >&2
  exit 1
fi
RESULT_URL="https://api.wavespeed.ai/api/v3/predictions/${PREDICTION_ID}/result"

# 2. Poll until the prediction reaches a final status.
BODY_FILE=$(mktemp)
trap 'rm -f "${BODY_FILE}"' EXIT
while true; do
  # Transient errors (429, 5xx) are retried, honoring Retry-After.
  HTTP_CODE=$(curl --silent --show-error --fail-with-body \
    --connect-timeout 10 --max-time 60 --retry 5 --retry-delay 2 \
    --output "${BODY_FILE}" --write-out '%{http_code}' \
    "${RESULT_URL}" \
    -H "Authorization: Bearer ${WAVESPEED_API_KEY}" || true)
  case "${HTTP_CODE}" in
    2??) ;;
    000|429|5??)  # dropped connection or temporary error: keep polling
      printf 'Task %s: HTTP %s, polling again in 10s\n' "${PREDICTION_ID}" "${HTTP_CODE}" >&2
      sleep 10; continue ;;
    *) printf 'Task %s: HTTP %s\n' "${PREDICTION_ID}" "${HTTP_CODE}" >&2
      cat "${BODY_FILE}" >&2; exit 1 ;;
  esac
  RESULT=$(jq 'if type == "object" and has("data") then .data else . end' "${BODY_FILE}")
  STATUS=$(printf '%s' "${RESULT}" | jq -r '.status // empty')

  case "${STATUS}" in
    completed) printf '%s\n' "${RESULT}" | jq '.outputs'; break ;;
    failed|cancelled|timeout|deleted)
      printf 'Task %s ended with status %s\n' "${PREDICTION_ID}" "${STATUS}" >&2
      printf '%s\n' "${RESULT}" | jq . >&2; exit 1 ;;
    *) sleep 2 ;;
  esac
done

Retry temporary errors only while polling, never the submit request. Errors, retries and timeouts

Parameters

Task Submission Parameters

Request Parameters

ParameterTypeRequiredDefaultRangeDescription
audiostringYes-1 ~ unlimited characters · pattern: ^https?://Public direct URL of the audio file. Upload a file or supply a URL.
language_codestringNo-pattern: ^[a-z]{2,3}$ISO-639-1 or ISO-639-3 language code. Omit for automatic detection.
secondary_language_codesarray<string>No-0 ~ 100 itemsUp to 100 additional ISO-639-1 or ISO-639-3 language codes expected in the audio, alongside language_code. Omit when not needed.
numbers_formatstringNo-digits, wordsWrite numbers as digits (42) or words (forty-two). Omit to use the model default.
diarizebooleanNofalse-Identify different speakers.
tag_audio_eventsbooleanNotrue-Include audio events such as laughter.
keytermsarray<string>No[]0 ~ 100 items · each item: 1 ~ 49 characters · pattern: ^[^\s<>{}\[\]\\]+(?:\s+[^\s<>{}\[\]\\]+){0,4}$Up to 100 recognition hints, each under 50 characters and at most 5 words. Additional charge applies.

Every model also accepts the global request options enable_sync_mode and enable_base64_output; see their pages for details.

Response Parameters

ParameterTypeDescription
codeintegerHTTP status code (e.g., 200 for success)
messagestringStatus message (e.g., “success”)
data.idstringUnique identifier for the prediction, Task Id
data.modelstringModel ID used for the prediction
data.outputsarrayOutput values, usually URL strings; some models return text strings or structured result objects (empty when status is not completed)
data.urlsobjectObject containing related API endpoints
data.statusstringTask status. completed is successful; failed, cancelled, timeout, and deleted are failure terminal statuses.
data.created_atstringISO timestamp of when the request was created (e.g., “2023-04-01T12:34:56.789Z”)
data.errorstringError message (empty if no error occurred)
data.timingsobjectObject containing timing details
data.timings.inferenceintegerInference time in milliseconds

Result Request Parameters

ParameterTypeRequiredDefaultDescription
idstringYes-Task ID

Result Response Parameters

ParameterTypeDescription
codeintegerHTTP status code (e.g., 200 for success)
messagestringStatus message (e.g., “success”)
dataobjectThe prediction data object containing all details
data.idstringUnique identifier for the prediction
data.modelstringModel ID used for the prediction
data.outputsarray<string | object>Array of generated outputs (empty when status is not completed). Items are usually URL strings, but may be text strings or structured result objects, depending on the model.
data.urlsobjectObject containing related API endpoints
data.statusstringStatus: completed is successful; failed, cancelled, timeout, and deleted are failure terminal statuses
data.created_atstringISO timestamp of when the request was created
data.errorstringError message (empty if no error occurred)
data.timingsobjectObject containing timing details
data.timings.inferenceintegerInference time in milliseconds
© 2026 WaveSpeedAI. All rights reserved.