OpenAPI spec for glossary management
Create a glossary
Authorizations
Body
namestringrequiredExample:
Name to be associated with the glossary.
My Glossary
source_langstring · enumrequiredExample:
The language in which the source texts in the glossary are specified.
en
Available options: target_langstring · enumrequiredExample:
The language in which the target texts in the glossary are specified.
de
Available options: entriesstringrequiredExample:
The entries of the glossary. The entries have to be specified in the format provided by the entries_format
parameter.
Hello Guten Tag
entries_formatstring · enumrequiredDefault:
The format in which the glossary entries are provided. Formats currently available:
tsv
(default) - tab-separated valuescsv
- comma-separated values
See Supported Glossary Formats for details about each format.
tsv
Example: tsv
Available options: Responses
application/json
application/json
201
400
401
403
404
413
415
429
456
500
503
529
List all glossaries
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 · enumoptionalDefault:
The requested format of the returned glossary entries. Currently, supports only text/tab-separated-values
.
text/tab-separated-values
Example: {"summary":"Tab-separated Values","value":{"in":"header","Accept":"text/tab-separated-values"}}
Available options: Responses
text/tab-separated-values
application/json
200
400
401
403
404
413
415
429
456
500
503
529
Last updated