API REFERENCE · CREATORS & CONTROL
Context
A one-sentence brief for the translator: who is on screen and what kind of video.
01.What context does
The translator reads it before every line -- so "Maya" stays a name instead of becoming a word, jargon resolves the right way, and running jokes keep their setup.
Context attaches at the same two scopes as Do Not Translate (creator · job), one sentence per scope; narrower wins -- The two scopes.
02.Set it
/v1/contextcurl -X PUT https://api.thefamiliarlab.com/v1/context \
-H "Authorization: Bearer $FAMILIAR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"sentence": "A chess channel: openings, blunders, and speedruns.",
"scope": "creator",
"scope_key": "cr_8f2k1q"
}'| FIELD | TYPE | REQUIRED | DESCRIPTION |
|---|---|---|---|
sentence | string | yes | The one-sentence brief; PUT replaces the scope's previous one. |
scope | string | yes | creator · job. |
scope_key | string | yes | The matching ID: creator_id or dub_id. |
03.Read it
/v1/context?scope=creator&scope_key=cr_8f2k1q{
"sentence": "A chess channel: openings, blunders, and speedruns.",
"scope": "creator",
"scope_key": "cr_8f2k1q",
"updated_at": "2026-08-13T15:12:44Z"
}A scope with no sentence returns 404.
04.Per-job context
The context field on POST /v1/dubs is a shortcut for the job scope -- one video, no separate write.
05.Access
The API is enterprise-only: private access under a Studio contract, with volume pricing, raised limits, ProRes masters on request, and a named point of contact. Book a call and your key is issued with the contract.