API REFERENCE · DUBBING

Metadata translation

Send the source title and description with the dub; each language's output arrives with its own translated pair, ready to post.

01.Send the source metadata

ON POST /v1/dubs
curl -X POST https://api.thefamiliarlab.com/v1/dubs \
  -H "Authorization: Bearer $FAMILIAR_API_KEY" \
  -F "file=@upload.mp4" \
  -F "target_langs=es,ja" \
  -F "metadata.title=Spring release: everything new" \
  -F "metadata.description=Full walkthrough. Code SPRING20 for 20% off.
00:00 Intro
02:41 The new editor
https://yourapp.com/changelog @yourapp #release"
TABLE 01 · METADATA FIELDS
FIELDTYPEREQUIREDDESCRIPTION
metadata.titlestringnoThe source title.
metadata.descriptionstringnoThe source description; multi-line, chapters and links included.

Both fields are translated with the same context and Do Not Translate lists as the video itself, so a catchphrase protected in the dub stays protected in the title.

02.Read the translated metadata

GET/v1/dubs/{dub_id}/metadata
200 · OK
{
  "dub_id": "dub_31xk9m",
  "source": {
    "title": "Spring release: everything new",
    "description": "Full walkthrough. Code SPRING20 for 20% off.\n00:00 Intro\n…"
  },
  "translations": [
    {
      "lang": "es",
      "title": "Lanzamiento de primavera: todas las novedades",
      "description": "Recorrido completo. Código SPRING20 para un 20% de descuento.\n00:00 Introducción\n…"
    },
    {
      "lang": "ja",
      "title": "春のリリース:新機能のすべて",
      "description": "全体の解説。コード SPRING20 で20%オフ。\n00:00 はじめに\n…"
    }
  ]
}

Translations land per language as each output completes; a language still rendering is absent from translations[]. Each pair is ready to paste into that language's upload form.

03.What survives untouched

The translator rewrites the prose and leaves the machinery alone:

TABLE 02 · PRESERVED VERBATIM
ELEMENTEXAMPLE
Linkshttps://yourapp.com/changelog
@handles@yourapp
#hashtags#release
Promo codesSPRING20
Chapter timestamps02:41 stays 02:41; the chapter label after it is translated.

04.Access

The API is enterprise-only: private access under a Studio contract, with volume pricing, raised limits, and a named point of contact for the integration. Book a call and your key is issued with the contract.