---
title: "Create a Glossary"
method: POST
path: "/v2/glossaries"
tags: ["ManageGlossaries"]
---

# Create a Glossary

`POST /v2/glossaries`

## Request body

- CreateGlossaryParameters
  - `name` string, required — Name to be associated with the glossary.
  - `source_lang` 'ar' | 'bg' | 'cs' | 'da' | 'de' | 'el' | 'en' | 'es' | 'et' | 'fi' | 'fr' | 'he' | 'hu' | 'id' | 'it' | 'ja' | 'ko' | 'lt' | 'lv' | 'nb' | 'nl' | 'pl' | 'pt' | 'ro' | 'ru' | 'sk' | 'sl' | 'sv' | 'th' | 'tr' | 'uk' | 'vi' | 'zh', required — The language in which the source texts in the glossary are specified.
  - `target_lang` 'ar' | 'bg' | 'cs' | 'da' | 'de' | 'el' | 'en' | 'es' | 'et' | 'fi' | 'fr' | 'he' | 'hu' | 'id' | 'it' | 'ja' | 'ko' | 'lt' | 'lv' | 'nb' | 'nl' | 'pl' | 'pt' | 'ro' | 'ru' | 'sk' | 'sl' | 'sv' | 'th' | 'tr' | 'uk' | 'vi' | 'zh', required — The language in which the target texts in the glossary are specified.
  - `entries` string, required — The entries of the glossary. The entries have to be specified in the format provided by the `entries_format` parameter.
  - `entries_format` 'tsv' | 'csv', required — 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](/docs/customize/managing-glossaries#entry-formats) for details about each format.

## Response `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.

- MonolingualGlossary
  - `glossary_id` string — A unique ID assigned to a glossary.
  - `name` string — Name associated with the glossary.
  - `ready` boolean — Indicates if the newly created glossary can already be used in `translate` requests. If the created glossary is not yet ready, you have to wait and check the `ready` status of the glossary before using it in a `translate` request.
  - `source_lang` 'ar' | 'bg' | 'cs' | 'da' | 'de' | 'el' | 'en' | 'es' | 'et' | 'fi' | 'fr' | 'he' | 'hu' | 'id' | 'it' | 'ja' | 'ko' | 'lt' | 'lv' | 'nb' | 'nl' | 'pl' | 'pt' | 'ro' | 'ru' | 'sk' | 'sl' | 'sv' | 'th' | 'tr' | 'uk' | 'vi' | 'zh' — The language in which the source texts in the glossary are specified.
  - `target_lang` 'ar' | 'bg' | 'cs' | 'da' | 'de' | 'el' | 'en' | 'es' | 'et' | 'fi' | 'fr' | 'he' | 'hu' | 'id' | 'it' | 'ja' | 'ko' | 'lt' | 'lv' | 'nb' | 'nl' | 'pl' | 'pt' | 'ro' | 'ru' | 'sk' | 'sl' | 'sv' | 'th' | 'tr' | 'uk' | 'vi' | 'zh' — The language in which the target texts in the glossary are specified.
  - `creation_time` string, date-time — The creation time of the glossary in the ISO 8601-1:2019 format (e.g.: `2021-08-03T14:16:18.329Z`).
  - `entry_count` integer — The number of entries in the glossary.

## Other responses

- `400` — Bad request. Please check error message and your parameters.
- `401` — Authorization failed. Please supply a valid `DeepL-Auth-Key` via the `Authorization` header.
- `403` — Forbidden. The access to the requested resource is denied, because of insufficient access rights. This error is also returned when the API key is scoped but does not include the scope required for this endpoint.
- `404` — The requested resource could not be found.
- `413` — The request size exceeds the limit.
- `415` — The requested entries format specified in the `Accept` header is not supported.
- `429` — Too many requests. Please wait and resend your request.
- `456` — Quota exceeded. The character limit has been reached.
- `500` — Internal error.
- `503` — Resource currently unavailable. Try again later.
- `529` — Too many requests. Please wait and resend your request.

---

[API](https://skmtc.net/deepl/apis/deepl-api-documentation.md) · [All operations](https://skmtc.net/deepl/apis/deepl-api-documentation/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/deepl/deepl-api-documentation/versions/3c422fcc9c54/schema)