Create a glossary
Create a new glossary in the organization. Its scope, approval workflow, and QA severities can be set here or updated later. Add languages and terms in follow-up calls.
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
Organization id (UUID) or id-embedded path slug.
Body
Human-readable glossary name, unique within the organization.
1 - 100"Brand Terms"
Optional summary of what this glossary covers.
500"Approved product and brand terminology for all UI surfaces."
Which projects the glossary applies to: all projects in the org, or only selected ones assigned to it. Defaults to all.
all, selected "all"
When true, term translations from non-approvers are stored as proposals until approved.
false
When true, org/glossary admins' edits are auto-approved even while approval is required.
true
Severity when a required term is missing from a translation: off, warning, or error. See the quality checks guide.
off, warning, error "warning"
Severity when a forbidden or deprecated term is used: off, warning, or error.
off, warning, error "error"

