Add or change a glossary term translation

Add or change a glossary term's translation in one language, its
translation note, or whether it is reviewed. Attributes left out keep
their values. A translation note can be set on a term without a
translation.

The language must be one of the glossary's languages. Every request
needs the right to submit translations for the language and a plan that
supports glossary editing. Changing reviewed, or the text of a
reviewed translation, also needs the right to review the language. Both
rights follow the glossary's permissions.

A translation change doesn't move the term's datetime_modified.

A 409 means the term is locked in the language, so its translation
can't change, reviewed: true is sent for a term with no translation in
the language, or the body's id names another term translation than the
path, as JSON:API requires. While a locked term's translation is
reviewed, as locking leaves it, a translation change from someone who
can't review the language is a 403 instead.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
^o:[a-zA-Z0-9._-]+:g:[a-zA-Z0-9_-]+:t:[a-zA-Z0-9]{16,}:l:[a-zA-Z0-9@_.-]+$

Format of composite id should be o:organization_slug:g:glossary_slug:t:term_hashid:l:language_code.

Body Params
data
object
required

Set glossary term translation body request details.

Responses

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/vnd.api+json