DEVELOPER GUIDE

Video Translation API — Build Multilingual Subtitle Pipelines at Scale

By Terry · Updated April 2026 · 12 min read

Why Integrate Video Translation via API?

Manual UI workflows break down at scale. If your team produces 50+ videos per week across multiple markets, a UI upload-download loop introduces bottlenecks, inconsistency, and human error. A video translation API solves three enterprise problems at once:

How the AdTransPro Translation Pipeline Works

Understanding the 5-stage pipeline helps you design integrations that handle errors gracefully and set realistic SLA expectations.

API Integration Examples

Note: Code below uses generic pseudocode patterns for illustration. Refer to the official AdTransPro API docs for exact endpoint paths, parameter names, and authentication details.

1. Single-File Translation

# Submit a single video for translation
# POST /v1/jobs
{
  "source_url": "https://cdn.yourbrand.com/videos/product-demo-en.mp4",
  "source_lang": "en",
  "target_langs": ["es", "zh-Hans", "ja", "pt-BR"],
  "glossary_id": "brand-q2-2026",
  "output_formats": ["srt", "vtt"],
  "frame_align": true,
  "webhook_url": "https://hooks.yourbrand.com/translation-complete"
}

# Response
{
  "job_id": "job_abc123",
  "status": "queued",
  "estimated_seconds": 45,
  "languages": ["es", "zh-Hans", "ja", "pt-BR"]
}

2. Batch Job (500+ Files)

# Submit a batch of videos
# POST /v1/jobs/batch
{
  "files": [
    { "id": "vid_001", "source_url": "https://cdn.yourbrand.com/ad-001-en.mp4" },
    { "id": "vid_002", "source_url": "https://cdn.yourbrand.com/ad-002-en.mp4" }
    // ... up to 500 entries
  ],
  "source_lang": "en",
  "target_langs": ["es", "de", "fr", "ja"],
  "glossary_id": "brand-q2-2026",
  "output_formats": ["srt"],
  "frame_align": true,
  "webhook_url": "https://hooks.yourbrand.com/batch-complete"
}

# Response
{
  "batch_id": "batch_xyz789",
  "job_count": 200,
  "status": "processing",
  "estimated_completion": "2026-04-07T11:45:00Z"
}

3. Webhook Payload (on Completion)

# Webhook fires when job completes
{
  "event": "job.completed",
  "job_id": "job_abc123",
  "batch_id": "batch_xyz789",
  "status": "completed",
  "download_urls": {
    "es":      { "srt": "https://cdn.adtranslate.pro/output/.../es.srt" },
    "zh-Hans": { "srt": "https://cdn.adtranslate.pro/output/.../zh-Hans.srt" },
    "ja":      { "srt": "https://cdn.adtranslate.pro/output/.../ja.srt" },
    "pt-BR":   { "srt": "https://cdn.adtranslate.pro/output/.../pt-BR.srt" }
  },
  "metadata": {
    "duration_seconds": 38,
    "source_lang": "en",
    "frame_align_accuracy": 0.947
  }
}

4. CI/CD Integration Pattern

# Example CI step (GitHub Actions pseudocode)
- name: Translate new ad creatives
  run: |
    # Find new MP4 files committed in this PR
    NEW_VIDEOS=$(git diff --name-only HEAD~1 | grep '.mp4')
    
    # Submit batch job and capture batch_id
    BATCH_ID=$(curl -s -X POST "$ADTRANS_API/v1/jobs/batch"       -H "Authorization: Bearer $ADTRANS_API_KEY"       -d "{ files: [...], target_langs: ['es','ja','de'] }"       | jq -r '.batch_id')
    
    echo "Batch $BATCH_ID submitted — webhook will push outputs to CDN"

# On webhook receipt: upload SRT files to CDN and tag PR with ✅

Performance Benchmarks

Internal benchmark, April 2026. Frame alignment measured against human-annotated ground truth for 1,000 ad creatives across 10 language pairs.

API Capability Comparison: AdTransPro vs. Alternatives

* Feature parity as of April 2026. Verify on vendor websites before purchasing.

Advanced API Features

API Access & Pricing

Quota is measured in video minutes, not API calls. At 5 target languages, AdTransPro API costs ~$0.02/min/language on the Studio plan — vs. $0.25–$0.75/min/language for LSP rates.

Frequently Asked Questions

Related Reading