Get Dubbing Transcript
Retrieves the transcript in the specified language of a specific end to end dubbing run using the provided run_id.
GET
Get Dubbed Run Transcript
This endpoint serves as a bridge between your media content and its written representation. When you’ve completed a dubbing run using Camb.ai’s powerful dubbing technology, it gives you access to all that valuable spoken content in text form, unlocking new possibilities for how you can use and share your content.
This code not only retrieves your transcript but also demonstrates proper error handling and different processing paths based on your chosen response type. Notice how we create a meaningful filename that includes both the run ID and language - this kind of attention to detail helps keep your transcripts organized when working with multiple videos or languages.
The
{language} path parameter is your language selector. It determines which linguistic version of your transcript you’ll receive - you can choose either the original source language or any of the target languages you’ve dubbed your content into.Understanding Response Options
The transcript endpoint gives you two distinct ways to receive your transcript data, each designed for different implementation scenarios:- Direct content delivery (
data_type=raw_data): The transcript text comes straight to you as{ "transcript": "<raw text>" }in the JSON response body. This immediate delivery is perfect for when you need to process or display the text right away in your application. - File-based delivery (
data_type=file): You receive{ "transcript": "<presigned url>" }linking to a ready-to-download transcript file. This approach works wonderfully when you need to store, share, or download the transcript as a distinct file.
transcript key — read it with response.json()["transcript"]. Your choice between these options depends on your workflow and how you intend to use the transcript data in your application.
Choosing the Right Format for Your Needs
Transcripts come in three carefully designed formats, each optimized for different applications:
The format you choose should align with how you plan to use the transcript. For example, if you’re adding subtitles to a web video player, WebVTT (
vtt) would be your best choice because of its native support in HTML5 environments. If you’re editing in professional software like Adobe Premiere, the srt format would integrate more seamlessly with your workflow.
Implementation Example: Bringing It All Together
Let’s walk through a complete example of how you might implement transcript retrieval in your application. This Python code sample demonstrates the process from request to application:Building a Complete Workflow
The transcript endpoint works best as part of a complete content processing workflow. Consider how it connects with these related endpoints:- Create Dubbing Run - Start the process by submitting your video for dubbing
- Check Dubbing Status - Monitor progress and determine when your transcript will be available
- Get Dubbed Media - Retrieve the dubbed media that corresponds to your transcript
Authorizations
Path Parameters
Language for this run. Pass a locale tag (en-us, fr-fr, es-es). Numeric language IDs still work but are deprecated. See all source languages.
Example:
"en-us"
Query Parameters
Last modified on July 25, 2026