All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
The major and minor version numbers reflect changes to the DeepL API (backward-incompatible and backward-compatible, respectively). The patch version number is used only for corrections to the OpenAPI specification, for example: typos, schema fixes, or adding examples.
2.18.0 - 2025-01-16
- Add new endpoint
/write/rephrase
which enables text corrections and adjustments in selected languages
2.17.0 - 2024-11-15
/translate
: addmodel_type
request parameter to request the model type (quality_optimized
,latency_optimized
, orprefer_latency_optimized
) to use for translation, and themodel_type_used
response parameter indicating the model type that used.
2.16.0 - 2024-07-25
- Add supported target language variant for text translation: Chinese
(traditional) (
ZH-HANT
). Traditional Chinese is currently supported only for text translation; document translation support is coming soon.
- The Chinese language codes returned in the
/languages
response for target languages were changed. While previously onlyZH
"Chinese (simplified)" was included,ZH-HANS
"Chinese (simplified)" is now listed too. Both language codes are supported for text and document translation.
- The target language code
ZH
is deprecated; insteadZH-HANS
orZH-HANT
should be used.
2.15.0 - 2024-07-03
- Add supported glossary language: Romanian (
ro
).
2.14.1 - 2024-06-18
- Text translation
context
parameter is now generally available (was alpha).
2.14.0 - 2024-05-08
- Added supported glossary languages: Danish (
'da'
), Norwegian (bokmål) ('nb'
), and Swedish ('sv'
).
2.13.0 - 2024-03-14
- Remove all properties from
/usage
except forcharacter_count
andcharacter_limit
; these are the only two properties included in the API response for the v2 API.
- Fixed some minor issues in specs that were violating OpenAPI specification.
2.12.0 - 2024-02-29
- Add supported glossary language: Korean (KO).
- Add supported language for text translation: Arabic (AR). Arabic is currently supported only for text translation; document translation support for Arabic is coming soon.
2.11.0 - 2023-08-03
- Add supported glossary languages: Portuguese (PT), Russian (RU), and Chinese (ZH).
2.10.0 - 2023-07-13
- Add JSON-format request bodies to all endpoints except document upload.
2.9.2 - 2023-06-20
- Japanese (JA) now supports formality.
2.9.1 - 2023-05-26
- Fix typo in
/glossaries/{glossary_id}
example and spec version number. - Move
description
parameter outside ofallOf
parameter.- Thanks to mikakruschel for the suggestion in #1.
- Transitive glossaries are now supported, bringing the number of supported glossary pairs from 8 to 28.
- Supported XLIFF version 2.1 is now explicitly stated.
- Add Korean and Norwegian (Bokmål) languages.
- Add XLIFF to supported document types.
- HTML handling is no longer in Beta.
- Removed limit on text parameters (was 50).
- Add support for EN (English) ←→ NL (Dutch) glossaries.
- Add formality options prefer_less and prefer_more.
- Add note to readme about Swagger UI simulator and CORS restrictions.
- Source and target language were mixed up in glossary example.
- Fix createGlossary example: remove punctuation.
- Add Ukrainian source and target languages.
- Add request body size limit to translateText description.
- Add "Simplified" label to ZH (Chinese) target language.
- Fix a typo in an example.
- Markdown fixes.
- Add support for EN (English) ←→ PL (Polish) glossaries.
- EN (English) ←→ IT (Italian) was missing from the list of supported glossary language pairs in the JSON OpenAPI spec.
- Add CSV entries format for creating glossaries.
- Rename some tags, reword some descriptions and label default values in descriptions.
- Add note about glossaries being immutable, and a workaround for modifying glossaries.
Initial release of the OpenAPI specification.