Look up glossary terms
Find the glossary terms that occur in one or more source strings, with their approved translations. Batched: pass every source string and every target language in one call.
Each match carries doNotTranslate, caseSensitive and usageStatus (preferred / deprecated / forbidden) so a translator — or an agent generating a translation — can honor terminology rules.
Constraints:
- Returns an empty object when the glossary feature is disabled for the org or the project.
- At most 100 source texts and 50 languages per request.
- Matching is whole-word where the term has word boundaries, substring otherwise (CJK/Thai).
Authorizations
API token: tsu_pat_… (PAT) or tsu_proj_… (project token). The token's granted RBAC permissions determine access; see each operation's x-permission.
Path Parameters
Project id (UUID) or id-embedded path slug.
Body
Source strings to scan for glossary terms (max 100 per call).
1 - 100 elementsTarget language codes to return translations for (max 50 per call).
1 - 50 elements1
