OpenAPI spec for glossary management

OpenAPI spec for v2 glossary features

This page was auto-generated from DeepL's OpenAPI file.

For more detail about glossary management, including information about request parameters, please see the Manage glossaries section.

List Language Pairs Supported by Glossaries

get

Retrieve the list of language pairs supported by the glossary feature.

Authorizations
Responses
200
A JSON object containing the language pairs in its `supported_languages` property.
application/json
{
  "supported_languages": [
    {
      "source_lang": "de",
      "target_lang": "en"
    },
    {
      "source_lang": "en",
      "target_lang": "de"
    }
  ]
}

Create a Glossary

post
Authorizations
Body
namestringRequired

Name to be associated with the glossary.

Example: My Glossary
source_langstring · enumRequired

The language in which the source texts in the glossary are specified.

Example: enPossible values:
target_langstring · enumRequired

The language in which the target texts in the glossary are specified.

Example: dePossible values:
entriesstringRequired

The entries of the glossary. The entries have to be specified in the format provided by the entries_format parameter.

Example: Hello Guten Tag
entries_formatstring · enumRequired

The format in which the glossary entries are provided. Formats currently available:

  • tsv (default) - tab-separated values
  • csv - comma-separated values

See Supported Glossary Formats for details about each format.

Default: tsvExample: tsvPossible values:
Responses
201
The function for creating a glossary returns a JSON object containing the ID of the newly created glossary and a boolean flag that indicates if the created glossary can already be used in translate requests.
application/json
{
  "glossary_id": "def3a26b-3e84-45b3-84ae-0c0aaf3525f7",
  "ready": true,
  "name": "My Glossary",
  "source_lang": "en",
  "target_lang": "de",
  "creation_time": "2021-08-03T14:16:18.329Z",
  "entry_count": 1
}

List all Glossaries

get

List all glossaries and their meta-information, but not the glossary entries.

Authorizations
Responses
200
JSON object containing a the glossaries.
application/json
{
  "glossaries": [
    {
      "glossary_id": "def3a26b-3e84-45b3-84ae-0c0aaf3525f7",
      "name": "My Glossary",
      "ready": true,
      "source_lang": "EN",
      "target_lang": "DE",
      "creation_time": "2021-08-03T14:16:18.329Z",
      "entry_count": 1
    }
  ]
}

Retrieve Glossary Details

get

Retrieve meta information for a single glossary, omitting the glossary entries.

Authorizations
Path parameters
glossary_idstringRequired

A unique ID assigned to the glossary.

Responses
200
JSON object containing the glossary meta-information.
application/json
{
  "glossary_id": "def3a26b-3e84-45b3-84ae-0c0aaf3525f7",
  "name": "My Glossary",
  "ready": true,
  "source_lang": "EN",
  "target_lang": "DE",
  "creation_time": "2021-08-03T14:16:18.329Z",
  "entry_count": 1
}

Retrieve Glossary Entries

get

List the entries of a single glossary in the format specified by the Accept header.

Authorizations
Path parameters
glossary_idstringRequired

A unique ID assigned to the glossary.

Header parameters
Acceptstring · enumOptional

The requested format of the returned glossary entries. Currently, supports only text/tab-separated-values.

Default: text/tab-separated-valuesExample: {"summary":"Tab-separated Values","value":{"in":"header","Accept":"text/tab-separated-values"}}Possible values:
Responses
200
The entries in the requested format.
text/tab-separated-values
Hello!	Guten Tag!

Delete a Glossary

delete

Deletes the specified glossary.

Authorizations
Path parameters
glossary_idstringRequired

A unique ID assigned to the glossary.

Responses
204
Returns no content upon success.

No content

Last updated