Manage glossaries using the v2 endpoints
v2
glossary endpoints, legacy endpoints that let you create and manage glossaries for a single language pair.See here for information on v3
endpoints, which allow you to create, manage, and edit glossaries with entries in multiple language pairs. See here for an overview of the difference.v2
endpoints to work with monolingual glossaries - glossaries that map phrases in one language to phrases in another language. If you’re new to glossaries, we suggest you use v3
instead. v3
allows you to work with multilingual glossaries, and it lets you edit any glossaries as well.
csv
file (glossary.csv
, with 2 example entries) via the command line using jq
. Note that you’ll need to install jq
if you haven’t already. Installation instructions for various operating systems are available here.
Accept
header.
/glossary-language-pairs
endpoint lists all the language pairs - the source and target languages - that glossaries support. Since glossaries now work for all languages DeepL supports, this list will be quite long. We recommend that you instead use the /languages endpoint.
v2
glossaries are immutable: once created, the glossary entries for a given glossary ID cannot be modified.
As a workaround for effectively editable glossaries, we suggest to identify glossaries by name instead of ID in your application and then use the following procedure for modifications: