Retrieve Glossary Entries | Deepl API documentation

Retrieve Glossary Entries Run in API Explorer

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL


        
          
            https://bump.sh/polo/hub/about-mcp/doc/deepl/mcp

Standard setup for AI tools providing an mcp.json file

{
  "Deepl MCP server": {
    "url": "https://bump.sh/polo/hub/about-mcp/doc/deepl/mcp"
  }
}

GET /v2/glossaries/{glossary_id}/entries

Auth header

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

Headers

Accept string

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

Value is text/tab-separated-values. Default value is text/tab-separated-values.

Path parameters

glossary_id string Required

A unique ID assigned to the glossary.

Responses

200 text/tab-separated-values

The entries in the requested format.
Hide headers attribute Show headers attribute
- X-Trace-ID
  
  A unique identifier for the request that can be included in bug reports to DeepL support.
400 application/json

Bad request. Please check error message and your parameters.
Hide headers attribute Show headers attribute
- X-Trace-ID
  
  A unique identifier for the request that can be included in bug reports to DeepL support.
Hide response attributes Show response attributes object
- message string
  
  Generic description of the error.
- detail string
  
  More specific description of the error.
401

Authorization failed. Please supply a valid DeepL-Auth-Key via the Authorization header.
Hide headers attribute Show headers attribute
- X-Trace-ID
  
  A unique identifier for the request that can be included in bug reports to DeepL support.
403

Forbidden. The access to the requested resource is denied, because of insufficient access rights.
Hide headers attribute Show headers attribute
- X-Trace-ID
  
  A unique identifier for the request that can be included in bug reports to DeepL support.
404

The requested resource could not be found.
Hide headers attribute Show headers attribute
- X-Trace-ID
  
  A unique identifier for the request that can be included in bug reports to DeepL support.
415

The requested entries format specified in the Accept header is not supported.
Hide headers attribute Show headers attribute
- X-Trace-ID
  
  A unique identifier for the request that can be included in bug reports to DeepL support.
429

Too many requests. Please wait and resend your request.
Hide headers attribute Show headers attribute
- X-Trace-ID
  
  A unique identifier for the request that can be included in bug reports to DeepL support.
500

Internal error.
Hide headers attribute Show headers attribute
- X-Trace-ID
  
  A unique identifier for the request that can be included in bug reports to DeepL support.
503

Resource currently unavailable. Try again later.
Hide headers attribute Show headers attribute
- X-Trace-ID
  
  A unique identifier for the request that can be included in bug reports to DeepL support.
529

Too many requests. Please wait and resend your request.
Hide headers attribute Show headers attribute
- X-Trace-ID
  
  A unique identifier for the request that can be included in bug reports to DeepL support.

GET /v2/glossaries/{glossary_id}/entries

curl \
 --request GET 'https://api.deepl.com/v2/glossaries/{glossary_id}/entries' \
 --header "Authorization: $API_KEY" \
 --header "Accept: {"in" => "header", "Accept" => "text/tab-separated-values"}"

Response examples (200)

Hello!	Guten Tag!

Response examples (400)

{
  "message": "Invalid glossary entries provided",
  "detail": "Key with the index 1 (starting at position 13) duplicates key with the index 0 (starting at position 0)"
}