API REFERENCE · CREATORS & CONTROL
Do Not Translate
Catchphrases, names, brands, and signature slang stay exactly as said -- in the dub, the subtitles, and the translated metadata.
01.How matching works
Matching is case-insensitive and applies wherever the phrase appears: the spoken dub, the subtitle files, and metadata translation. Entries attach at one of the three scopes (creator · stream · job); narrower wins -- The three scopes.
02.Add an entry
/v1/dont-translatecurl -X POST https://api.thefamiliarlab.com/v1/dont-translate \
-H "Authorization: Bearer $FAMILIAR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"phrase": "GG",
"scope": "creator",
"scope_key": "cr_8f2k1q"
}'
{
"entry_id": "dnt_5rp30x",
"phrase": "GG",
"scope": "creator",
"scope_key": "cr_8f2k1q"
}| FIELD | TYPE | REQUIRED | DESCRIPTION |
|---|---|---|---|
phrase | string | yes | The exact phrase to protect. |
scope | string | yes | creator · stream · job. |
scope_key | string | yes | The matching ID: creator_id, session_id, or dub_id. |
03.List entries
/v1/dont-translate?scope=creator&scope_key=cr_8f2k1q{
"data": [
{ "entry_id": "dnt_5rp30x", "phrase": "GG", "scope": "creator", "scope_key": "cr_8f2k1q" }
],
"has_more": false
}Both query parameters are required together -- a list is always one scope's view, which is exactly what a settings screen in your product renders.
04.Remove an entry
/v1/dont-translate/{entry_id}Removal applies to the next dub; jobs already translating keep the list they started with.
05.Seeded defaults
06.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.