Skip to main content
The Managed Dub API can produce text deliverables — subtitles, captions, and transcripts — without rendering or delivering a dubbed video. This is the subtitle-only (deliverables-only) flow. It uses the same POST /dubbing/job endpoint as a full dubbing job (see the Submit Dubbing Job endpoint in the API Reference). The difference is entirely in the request body: you request one or more additional products and omit the dubbed-video export path.

How it works

A dubbing job always runs intake, transcription, and translation against the source video. What the job delivers depends on the request: For a subtitle-only job you therefore set additionalProducts and leave exportPath unset.
A request must contain at least one of exportPath or additionalProducts. A job with neither has nothing to deliver and will fail at delivery time.

Available subtitle & transcript products

Each entry in additionalProducts has a product type and an assetPath — the s3:// destination where Deepdub writes the finished file.

Request

1

Build the request body

Provide the source video and the target locale, then list the subtitle/transcript products you want under additionalProducts. Do not set exportPath.
2

Submit the job

Response

Use the requestId to track the job.

Tracking status

Poll the GET /dubbing/job/{requestId} endpoint (see Get Dubbing Job in the API Reference) to follow the job. Each entry in the returned additionalProducts reports its delivery state:
  • PENDING_DELIVERY — awaiting delivery
  • DELIVERED — written to the requested assetPath
Once every requested product reports DELIVERED, the subtitle files are available at their assetPath locations.

Notes

  • All S3 paths (sourceVideoPath, assetPath) must start with s3:// and be in a bucket Deepdub is authorized to read from and write to.
  • Authenticate every request with the x-api-key header. Contact your account manager to obtain an API key.
  • The base URL is https://dubbing.deepdub.app.