Skip to content

roadmap-and-release-notes.mdx

Latest commit

 

History

History
149 lines (124 loc) · 13.5 KB

roadmap-and-release-notes.mdx

File metadata and controls

149 lines (124 loc) · 13.5 KB
title Roadmap and release notes
description The latest features and improvements in the DeepL API, plus what's coming next
rss true
- Add more events to audit logs for Pro API customers (API key management, cost control and usage limit changes) - Translation Memory via API - `v3/languages` endpoint with improved language code handling and additional functionality ## March 27 - Write API Improvements - Improved overall quality of the models used in [DeepL API for Write](/api-reference/improve-text/) - Expanded Write `target_lang` support to Japanese (`JA`), Korean (`KO`) and simplified Chinese (`ZH` or `zh-Hans`) - Expanded Write support for `writing_style` and `tone` to Spanish (`ES`), Italian (`IT`), French (`FR`), Portuguese (`pt-PT`) and Brazilian Portuguese (`pt-BR`) - Allow sending Write texts in multiple source languages in the same request when no `target_lang` is set

March 26 - Expanded Style Rules API

  • Added 5 new endpoints for style rule list operations: POST /v3/style_rules, GET /v3/style_rules/{style_id}, PATCH /v3/style_rules/{style_id}, DELETE /v3/style_rules/{style_id}, and PUT /v3/style_rules/{style_id}/configured_rules.
  • Added 4 new endpoints for managing custom instructions within style rule lists: POST /v3/style_rules/{style_id}/custom_instructions, GET /v3/style_rules/{style_id}/custom_instructions/{instruction_id}, PUT /v3/style_rules/{style_id}/custom_instructions/{instruction_id}, and DELETE /v3/style_rules/{style_id}/custom_instructions/{instruction_id}.
  • See the full API reference here.

March 24 - Write API Character Count Fix

  • Fixed an issue where some DeepL API for Write requests under-counted usage.
  • All characters in Write requests are now correctly counted for billing and reporting purposes.
## February 18 - Additional Languages in `v2/languages` - New languages added to the [v2/languages endpoint](/api-reference/languages), bringing totals to **101 source languages** and **106 target languages**. - These languages were already supported for translation; this change improves automatic discoverability for API clients. - Note: 12 supported languages using three-letter base codes (e.g. ACE, CEB, CKB) are not yet included in `v2/languages` for backwards compatibility, but will be available in the upcoming `v3/languages` endpoint. ## January 20 - Legacy Auth Deprecation

Query parameter and request body authentication methods are now deprecated.

  • API Free users: All requests using legacy auth now return 403 Forbidden.
  • API Pro users: Brownout period active with intermittent 403 responses. Full deprecation in early February 2026.

Use the DeepL-Auth-Key header instead.

January 8 - 81 New Languages in GA

  • Promoted all 81 beta languages to standard language support. These languages are now part of the main source and target language lists.
  • Note that these languages only work with quality_optimized model or when no model is specified, and are not compatible with latency_optimized requests.
  • The enable_beta_languages parameter is maintained for backward compatibility but has no effect.

See here for the complete language list.

## Q4 2025 - Added API reference for the Voice API - Add contextual menu in the to make it easier to copy any API documentation page as context for AI tools - Add support for style rules in the API to programmatically get your created style rules and translate with them. - Overhauled the tag-handling algorithm that backs translation of XML and HTML in the DeepL API. To enable it and benefit from all the improvements, set the `tag_handling_version` parameter to `v2` in the text translation API. See [here](../xml-and-html-handling/tag-handling-v2) for more information. - Added new usage analytics endpoint in the Admin API, including key-level reporting. See [here](/api-reference/admin-api/get-usage-analytics) for more details - Enabled support for multiple admins in an API subscription - Added support for 75 new languages, initially through the `enable_beta_languages` parameter, for text and document translation. Beta languages are not billed during the beta phase and do not yet support glossaries or formality. See [here](../getting-started/supported-languages#beta-languages) for more information - Added HE, TH and VI to the languages endpoint, since they are now also available in document translation - Added 6 additional beta languages, for text and document translation. See the previous note about 75 new languages. - Added a new parameter to the text translation API to allow custom instructions, making it possible to customize the translation behavior (e.g. ["Use a friendly, diplomatic tone"]) - Added support for JPEG and PNG images in [document translation](/api-reference/document), currently in Beta.

Q3 2025

  • Creation of an admin API, making it possible to manage API keys programmatically. See here for more information
  • Added support for new language: ES-419 (Latin American Spanish). For this release, this language will be available for the API in next-gen models only. See here for more information.
  • Refreshed our API documentation and added new try-it explorers to support interacting with our APIs. See here to try it out!

Q2 2025

  • Added support for new language: TH (Thai). For this release, this language will only support text translation. See here for more information.
  • Added support for new languages: HE (Hebrew) and VI (Vietnamese). For this release, these languages will be available for Pro v2 API in next-gen models only. See here for more information.
  • Added improvements to API glossaries, including the ability to edit glossaries and create multilingual glossaries. Learn more here.
  • Improvements to the /usage endpoint for Pro API customers (API reference)
  • Improvements to key-level usage reporting, making it possible to pull reports with a custom date range and to group data by calendar day. Learn more here.

Q1 2025

  • Added support for API key-level usage limits, making it possible to set a character limit at the API key-level. Learn more here.
  • DeepL API for Write is generally available to Pro API customers, making it possible to improve texts in (at the time of release) 6 different languages. Learn more and get started here.
## Q4 2024 - Added the `model_type` parameter, allowing users to translate text with DeepL's "next-gen" translation models. More information can be found [here](/api-reference/translate#about-the-model_type-parameter).

Q3 2024

  • Added the show_billed_characters parameter for text translation, allowing users to optionally include the number of billed characters in the API response. Learn more here.
  • Added support for a new language for text translation: ZH-HANT (Traditional Chinese). As of this initial release, document translation is not supported for Traditional Chinese. More information is available here.
  • An official Ruby client library, evolved from a community-written library by Daniel Herzog. You can download it here or find the source code on our GitHub page.

Q2 2024

  • Added support for DOCX and PPTX document minification to the PHP client library, making it possible for users to translate documents that exceed DeepL's file size limit due to embedded media. Learn more here.
  • Added support for API key-level usage reporting. More information is available in the multiple API keys guide.
  • Launched DeepL Pro in 165 new markets, bringing the total number of markets where DeepL Pro is available to 228. This means users with billing addresses in these markets can create DeepL Pro API and Free API subscriptions.
  • Added support for new glossary languages: DA (Danish), NB (Norwegian Bokmål), and Swedish (SV).
  • Moved the context parameter from alpha status to general availability. More information about the context parameter is available in the "Request body descriptions" table here.
  • Added support for SRT (srt) files in document translation.

Q1 2024

  • Added support for multiple API keys in a single account for Pro API and Free API users. More information is available in the multiple API keys guide.
  • Added support for a new language for text translation: AR (Arabic). As of this initial release, document translation is not supported for Arabic. More information is available here.
  • Added support for Korean (KO) as a glossary language, increasing the number of supported glossary language pairs from 55 to 66.
## Q4 2023 - Added support for Microsoft Excel (`xlsx`) files in [document translation](/api-reference/document). - Released the `context` parameter as an [alpha feature](/docs/getting-started/alpha-and-beta-features) for text translation (see [Request Body Descriptions table](/api-reference/translate#request-body-descriptions) for more information).

Q3 2023

  • Launched DeepL Pro in South Korea (blog post here). This means users with billing addresses in South Korea can create DeepL Pro API and Free API subscriptions.
  • Added support for Portuguese (PT), Russian (RU), and Chinese (ZH) as glossary languages, increasing the number of supported glossary language pairs from 28 to 55.
  • Added support for JSON-encoded requests for all remaining endpoints (note that document upload for document translation still requiresmultipart/form-data).

Q2 2023

Q1 2023

  • Released an official DeepL Custom Connector for Microsoft Power Automate.
  • Added support for glossaries in any combination of two languages from the following list: EN (English), DE (German), FR (French), IT (Italian), PL (Polish), NL (Dutch), ES (Spanish, JA (Japanese). This represents an increase from 8 to 28 supported glossary language pairs.
  • Added XLIFF as a document translation format (note that only documents from version 2.0 are supported, and there is no support for the legacy 1.2 format).
  • Added support for new languages for text and document translation: KO (Korean) and NB (Norwegian Bokmål). Blog post here.
## Q4 2022 - Moved [HTML handling](/docs/xml-and-html-handling/html) out of beta after fixing the most commonly reported user issues. - Released an official [Java client library](https://github.com/DeepLcom/deepl-java). - Added support for JSON-encoded requests for [text translation](/api-reference/translate), [usage](/api-reference/usage-and-quota), and [languages](/api-reference/languages) endpoints.

Q3 2022

Before Q3 2022