Get Transcription Result

GET

transcription-result

{run_id}

curl --request GET \
  --url https://client.camb.ai/apis/transcription-result/{run_id} \
  --header 'x-api-key: <api-key>'

const options = {method: 'GET', headers: {'x-api-key': '<api-key>'}};

fetch('https://client.camb.ai/apis/transcription-result/{run_id}', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://client.camb.ai/apis/transcription-result/{run_id}",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "GET",
  CURLOPT_HTTPHEADER => [
    "x-api-key: <api-key>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

{
  "transcript": [
    {
      "start": 123,
      "end": 123,
      "text": "<string>",
      "speaker": "<string>"
    }
  ]
}

{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>"
    }
  ]
}

Fetches the result of a completed transcription run.

By default (no query params) you get the structured JSON transcript: an object whose transcript field is an array of { start, end, text, speaker } segments.
When you pass format_type and/or data_type, the transcript is exported in the requested subtitle format and returned as { "transcript": <presigned url | raw text> }, the same parameter values and response shape as the dubbing Get Dubbing Transcript endpoint.

Use the run_id returned when you created the transcription run. The run must have finished processing and must be a transcription project.

Choosing your output

Parameter	Values	Behaviour
(none)	n/a	Structured JSON transcript: `{ "transcript": [ {start, end, text, speaker}, ... ] }`
`data_type=file`	`srt` / `vtt` / `txt` via `format_type` (default `txt`)	`{ "transcript": "<presigned url>" }`: a downloadable file
`data_type=raw_data`	`srt` / `vtt` / `txt` via `format_type` (default `txt`)	`{ "transcript": "<raw text>" }`: the rendered text inline

format_type (srt/vtt/txt) and data_type (raw_data/file) use the exact same values as the dubbing /transcript endpoint, and the export responses are identical.

Implementation Example

import requests

API_KEY = "your_api_key_here"
RUN_ID = 12345

url = f"https://client.camb.ai/apis/transcription-result/{RUN_ID}"
headers = {"x-api-key": API_KEY}

# 1) Default: structured JSON transcript
result = requests.get(url, headers=headers).json()
for segment in result["transcript"]:
    print(f"[{segment['start']} - {segment['end']}] {segment['speaker']}: {segment['text']}")

# 2) Export: presigned URL to an SRT file
srt = requests.get(
    url, headers=headers, params={"format_type": "srt", "data_type": "file"}
).json()
file_url = srt["transcript"]
print(f"SRT file: {file_url}")

# 3) Export: raw VTT text inline
vtt = requests.get(
    url, headers=headers, params={"format_type": "vtt", "data_type": "raw_data"}
).json()
print(vtt["transcript"][:150])

Understanding the Response Structure

The response is always a JSON object with a single transcript field. Its value depends on the parameters.

Default: structured transcript (no params)

{
  "transcript": [
    { "start": 5.0,  "end": 12.0, "text": "Welcome to our discussion on AI.", "speaker": "SPEAKER_0" },
    { "start": 13.0, "end": 18.0, "text": "Thank you for having me.",         "speaker": "SPEAKER_1" }
  ]
}

Field	Description
`start`	Start time of the segment (seconds)
`end`	End time of the segment (seconds)
`text`	Transcribed text for the segment
`speaker`	Speaker identifier

Export: file (`data_type=file`)

{ "transcript": "https://storage.example.com/.../output_transcript.srt?..." }

transcript is a presigned URL to the rendered file. The file content matches your format_type:

TXT (`format_type=txt`)

[00:00:05 - 00:00:12] Speaker 1: Welcome to our discussion on AI.
[00:00:13 - 00:00:18] Speaker 2: Thank you for having me.

SRT (`format_type=srt`)

1
00:00:05,000 --> 00:00:12,000
Speaker 1: Welcome to our discussion on AI.

2
00:00:13,000 --> 00:00:18,000
Speaker 2: Thank you for having me.

VTT (`format_type=vtt`)

WEBVTT

00:00:05.000 --> 00:00:12.000
Speaker 1: Welcome to our discussion on AI.

00:00:13.000 --> 00:00:18.000
Speaker 2: Thank you for having me.

Export: raw data (`data_type=raw_data`)

The same rendered content is returned inline as a string:

{ "transcript": "1\n00:00:05,000 --> 00:00:12,000\nSpeaker 1: Welcome to our discussion on AI.\n\n..." }

The presigned file URL expires after 24 hours, so download your file soon.

Fetching Multiple Runs at Once

Need transcripts for several runs? Use Fetch Transcription Run Results (POST /apis/transcription-results). It returns the structured { start, end, text, speaker } transcript per run and does not take format_type / data_type.

Building a Complete Workflow

Create Transcription: submit your media for transcription
Poll Transcription Status: determine when your transcript is ready

Authorizations

x-api-key

string

header

required

The x-api-key is a custom header required for authenticating requests to our API. Include this header in your request with the appropriate API key value to securely access our endpoints. You can find your API key(s) in the 'API' section of our studio website.

Path Parameters

run_id

integer

required

The unique identifier for the run, which was generated during the transcription creation process and returned upon task completion. The unique identifier for the run, which was generated during the creation process and returned upon task completion.

Query Parameters

format_type

enum<string> | null

default:txt

Subtitle format for the transcript export: srt, vtt or txt. When omitted (and data_type is also omitted) the structured JSON transcript is returned instead of an exported file.

Available options:

srt,

vtt,

txt

data_type

enum<string> | null

default:file

How the exported transcript is returned once format_type/data_type is set: file returns a presigned URL, raw_data returns the raw text. Same values and response shape as the dubbing /transcript endpoint. In export mode the effective defaults are format_type=txt, data_type=file.

Available options:

raw_data,

file

Response

Successful Response

transcript

Structured dialogue array by default; a string (presigned URL for data_type=file, or raw text for data_type=raw_data) in export mode.

Hide child attributes

transcript.start

number<float>

required

The start time (in seconds) of the dialogue.

transcript.end

number<float>

required

The end time (in seconds) of the dialogue.

transcript.text

string

required

The actual text content of the dialogue spoken by the speaker.

transcript.speaker

string

required

The name or identifier of the speaker delivering the dialogue.

Last modified on July 26, 2026

Fetch Transcription ResultsRetrieves the results of multiple transcription runs using the provided run IDs in the request body.

Get Transcription Result

curl --request GET \
  --url https://client.camb.ai/apis/transcription-result/{run_id} \
  --header 'x-api-key: <api-key>'

const options = {method: 'GET', headers: {'x-api-key': '<api-key>'}};

fetch('https://client.camb.ai/apis/transcription-result/{run_id}', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://client.camb.ai/apis/transcription-result/{run_id}",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "GET",
  CURLOPT_HTTPHEADER => [
    "x-api-key: <api-key>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

{
  "transcript": [
    {
      "start": 123,
      "end": 123,
      "text": "<string>",
      "speaker": "<string>"
    }
  ]
}

{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>"
    }
  ]
}

Getting Started

Models

Tutorials

SDK Guides

Hosting Platforms

Integrations

API Reference

Other Products

Release Logs

Get Transcription Result

Choosing your output

Implementation Example

Understanding the Response Structure

Default: structured transcript (no params)

Export: file (`data_type=file`)

TXT (`format_type=txt`)

SRT (`format_type=srt`)

VTT (`format_type=vtt`)

Export: raw data (`data_type=raw_data`)

Fetching Multiple Runs at Once

Building a Complete Workflow

Authorizations

Path Parameters

Query Parameters

Response

​Choosing your output

​Implementation Example

​Understanding the Response Structure

​Default: structured transcript (no params)

​Export: file (data_type=file)

​TXT (format_type=txt)

​SRT (format_type=srt)

​VTT (format_type=vtt)

​Export: raw data (data_type=raw_data)

​Fetching Multiple Runs at Once

​Building a Complete Workflow

Authorizations

Path Parameters

Query Parameters

Response

Choosing your output

Implementation Example

Understanding the Response Structure

Default: structured transcript (no params)

Export: file (`data_type=file`)

TXT (`format_type=txt`)

SRT (`format_type=srt`)

VTT (`format_type=vtt`)

Export: raw data (`data_type=raw_data`)

Fetching Multiple Runs at Once

Building a Complete Workflow