Rename a glossary

Rename a glossary. The slug and the source language never change, so
stored glossary and term IDs keep working.

Only organization administrators can rename glossaries, and only on a plan
that supports glossary upload.

A 409 means the glossary's stored state refuses the rename: it is
archived or it has no resource. A body whose id names another glossary
than the path gets a 409 too, as JSON:API requires.

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_-]+$

Format of composite id should be o:organization_slug:g:glossary_slug.

Body Params
data
object
required

Update glossary 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