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.
- Document
X-Trace-IDresponse header returned by all API endpoints for request tracking and debugging - Add new parameters to the text translation API:
enable_beta_languagesandcustom_instructions - Add new CRUD endpoints for
/v3/style_rules - Add new endpoint
GET /v3/translation_memoriesfor listing translation memories - Add new parameters
translation_memory_idandtranslation_memory_thresholdto/v2/translate - Add
format: uuidtoStyleIdschema
- Fixes/development changes to the voice API.
- Changed the voice paths in the
voice.asyncapi.*files to use/v3/voice/* - Renamed
SourceDataChunkandEndOfSourceDatatoSourceMediaChunkandEndOfSourceMedia
- Changed the voice paths in the
- Fixes the usage endpoint response object name. Should be
key_usagesandkey_and_day_usagesinstead ofgrouped_usage - Add all supported languages to Translate API
source_langandtarget_langspecs - Merge redundant
SourceLanguageTextandTargetLanguageTextschemas intoSourceLanguageandTargetLanguageto eliminate duplication
- Removed the
openapi_gitbook.yamlfile due to redundancy. Please useopenapi.yamlgoing forward
- Add
speech_to_text_millisecondsfield to developer key usage limits in/v2/admin/developer-keys/limitsendpoint andApiKeyresponse schema
3.9.0 - 2025-12-11
- Add
speech_to_text_millisecondsfield to usage reports and analytics components - Add
speech_to_text_milliseconds_countandspeech_to_text_milliseconds_limitfields to/v2/usageresponse for API Pro users - Add
billing_unit,api_key_unit_count, andaccount_unit_countfields to product usage items in/v2/usageresponse
3.8.0 - 2025-11-26
- Fixes/development changes to the voice API. Note that this API is under active develpoment and not yet stable.
- Change voice path to be
/v3/voice/realtimeand/v3/voice/realtime/connect - Renamed voice parameter from
media_content_typetosource_media_content_type - Allow more
formalityvalues on voice endpoints
- Change voice path to be
3.7.0 - 2025-11-10
- Add new endpoints
/v1/voice/realtime(REST) and/v1/voice/realtime/connect(WebSocket) which enable real-time voice transcription and translation via WebSocket streaming - Adds AsyncAPI specification -
voice.asyncapi.yamlandvoice.asyncapi.json- documenting the Voice WebSocket streaming protocol
3.6.1 - 2025-11-06
- Hebrew (
HE), Thai (TH), and Vietnamese (VI) are now included in the/v2/languagesendpoint response as they now support document translation in addition to text translation
3.6.0 - 2025-10-29
- Add new parameter
tag_handling_versionto/v2/translate
3.5.0 - 2025-10-27
- Add new endpoint
v2/admin/analyticswhich enables admins to retrieve usage statistics across their organization
3.4.2 - 2025-10-06
- Latin American Spanish (
ES-419) is now supported as a target language option for Document translation./v2/languagesnow includesES-419as a valid target language option.
3.4.1 - 2025-07-31
- Add note for boolean values about how to input for URL-encoded forms
3.4.0 - 2025-07-16
- Add new endpoints
/v2/admin/developer-keyswhich enables management of developer keys within an organization.
3.3.1 - 2025-07-16
- Added
application/x-www-form-urlencodedContent-Type to thereplaceDictionaryendpoint.- Thanks to danielesser for the report in #35.
3.3.0 - 2025-06-25
- Updated the possible error responses for the /v2 and /v3 glossary endpoints
including:
- Removing any errors that are not valid responses for the API
- Updating the
QuotaExceededGlossariesdescription as it is returned when the glossary creation limit has been reached
3.2.0 - 2025-06-03
- Added updated language support for document translation:
- Target language variant: Chinese (traditional) (
ZH-HANT) - Source and target language: Arabic (
AR)
- Target language variant: Chinese (traditional) (
- Added updated language support for text translation for Hebrew (
HE), Thai (TH), and Vietnamese (VI). These languages are only supported for text translation, document translation support is coming soon. - Added updated source and target for glossaries. All languages supported for
text translation are now supported for glossaries now including:
Arabic (
AR), Bulgarian (BG), Czech (CS), Greek (EL), Estonian (ET), Hebrew (HE), Hungarian (HU), Indonesian (ID), Lithuanian (LT), Latvian (LV), Slovak (SK), Slovenian (SL), Thai (TH), Turkish (TR), Ukrainian (UK), and Vietnamese (VI).
3.1.1 - 2025-05-23
- Fixed incorrect placement of UsageResponse schema.
3.1.0 - 2024-05-20
/v2/usage: Now returns a detailed response for API Pro users, including per-product usage and billing period information. For API users not on the Pro plan, the response remains unchanged and only includescharacter_countandcharacter_limit.
3.1.0 - 2024-05-20
- Fixed new server URLs to avoid double slash in paths
3.0.1 - 2025-04-24
- Fixed new server URLs to avoid double slash in paths
3.0.0 - 2025-04-24
- Add new endpoints
/v3/glossarieswhich enables management of new, editable and multilingual glossaries- This required renaming some existing components in the spec, hence the major version upgrade. All functionality is backwards compatible.
- Moved
/v2/and/v3/from the Server URL into the endpoint paths, as we support multiple versions now
2.18.0 - 2025-01-16
- Add new endpoint
/write/rephrasewhich enables text corrections and adjustments in selected languages
2.17.0 - 2024-11-15
/translate: addmodel_typerequest parameter to request the model type (quality_optimized,latency_optimized, orprefer_latency_optimized) to use for translation, and themodel_type_usedresponse 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
/languagesresponse 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
ZHis deprecated; insteadZH-HANSorZH-HANTshould be used.
2.15.0 - 2024-07-03
- Add supported glossary language: Romanian (
ro).
2.14.1 - 2024-06-18
- Text translation
contextparameter 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
/usageexcept forcharacter_countandcharacter_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
descriptionparameter outside ofallOfparameter.- 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.