My first paragraph.
Example response CopyMy first paragraph.
[Customized XML outline detection](https://developers.deepl.com/docs/xml-and-html-handling/customized-xml-outline-detection) [New: XML/HTML handling v2](https://developers.deepl.com/docs/xml-and-html-handling/tag-handling-v2) ⌘I --- # Making API calls from client-side JavaScript - DeepL Documentation [Skip to main content](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#content-area) [Join the Developer Community on DeepL Bridges](https://dee.pl/7iwrt) [DeepL Documentation home page](https://developers.deepl.com/) Search... ⌘K Search... Navigation Cookbook Making API calls from client-side JavaScript [Documentation](https://developers.deepl.com/docs/getting-started/intro) [API Reference](https://developers.deepl.com/api-reference/translate) On this page * [Rationale](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#rationale) * [When to use a quick proxy](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#when-to-use-a-quick-proxy) * [Node.js Proxy Server](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#node-js-proxy-server) * [Quick & dirty PHP proxy](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#quick-%26-dirty-php-proxy) * [Screenshots](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#screenshots) * [Node.js proxy](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#node-js-proxy) * [PHP proxy](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#php-proxy) These proxies are intended for prototyping and frontend testing. For production environments, consider implementing your own backend service with additional security measures and rate limiting. [](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#rationale) Rationale ---------------------------------------------------------------------------------------------------- The DeepL API does not permit calls from client-side JavaScript - that is, from JavaScript running in a browser. This policy exists to keep your API key safe. When you place a call from your website directly to the DeepL API, that call needs to include your API key. Anyone using your website could look at the network calls or your code itself, find your API key, and use it themselves. For this and other security considerations, DeepL [does not enable the CORS headers](https://developers.deepl.com/docs/best-practices/cors-requests) you would need to call the API from a webpage hosted on your origin. The industry-standard approach is to call APIs like DeepL’s from a back-end service. DeepL enforces this best practice to keep your credentials secure. [](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#when-to-use-a-quick-proxy) When to use a quick proxy ------------------------------------------------------------------------------------------------------------------------------------ But what do you do if you want to use the API quickly, in a prototype, a demo, or a hackathon, where you need to get up and running fast? What if you don’t have easy access to a server? For such situations, here are two solutions. [](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#node-js-proxy-server) Node.js Proxy Server -------------------------------------------------------------------------------------------------------------------------- [GitHub - DeepLcom/deepl-api-nodejs-proxy\ ----------------------------------------\ \ DeepL API Node.js Proxy on GitHub](https://github.com/DeepLcom/deepl-api-nodejs-proxy) This full-featured proxy server supports all DeepL API endpoints, including text translation, document translation, and glossaries. Built with Node.js and Express with minimal dependencies, it handles CORS headers for you and keeps your API key secure. It even includes an interactive web demo for testing translations right in your browser. This proxy includes an interactive setup wizard to get you started quickly. Clone the repo, run the setup, and start sending requests from your browser. Check out the [GitHub repository](https://github.com/DeepLcom/deepl-api-nodejs-proxy) for full setup instructions and Docker support. [](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#quick-&-dirty-php-proxy) Quick & dirty PHP proxy -------------------------------------------------------------------------------------------------------------------------------- If you’re just using our `/translate` endpoint and want an even quicker solution, or if you don’t use node.js, you could use the PHP code below to create an instant proxy server. If PHP is not already installed on your machine, you can download and install it at [php.net](https://www.php.net/downloads.php) . The PHP script takes the parameters in the query string and passes them into a `POST` request to `/translate`. It does not check that the parameters are valid and does not support any other endpoints, although you could modify it to do so. To use this while developing on your local machine: * replace `{your API key here}` with your actual API key * create a file in your favorite directory with the PHP code below * go to your terminal and visit that directory * type `php -S localhost:8000` Your JavaScript can then access the DeepL API at `http://localhost:8000/php-proxy.php`. For example, to send a translation request with `text` and `target_lang`: Copy const url = `http://localhost:8000/deepl-proxy.php?text=${encodeURIComponent(text)}&target_lang=${encodeURIComponent(targetLang)}`; const response = await fetch(url); const result = await response.text(); Here is the PHP script: Copy [\ 'method' => 'POST',\ 'header' => "Authorization: DeepL-Auth-Key " . $apiKey . "\r\n" .\ "Content-Type: application/x-www-form-urlencoded\r\n",\ 'content' => $data\ ]\ ]); echo file_get_contents($apiUrl, false, $context); ?> [](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#screenshots) Screenshots -------------------------------------------------------------------------------------------------------- ### [](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#node-js-proxy) Node.js proxy   ### [](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy#php-proxy) PHP proxy  [Usage Analytics Dashboard](https://developers.deepl.com/docs/learning-how-tos/cookbook/usage-analytics-dashboard) [How to Use the Context Parameter Effectively](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter) ⌘I --- # July 2024: Deprecation of insecure cipher suites - DeepL Documentation [Skip to main content](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#content-area) [Join the Developer Community on DeepL Bridges](https://dee.pl/7iwrt) [DeepL Documentation home page](https://developers.deepl.com/) Search... ⌘K Search... Navigation Breaking changes (change notices) July 2024: Deprecation of insecure cipher suites [Documentation](https://developers.deepl.com/docs/getting-started/intro) [API Reference](https://developers.deepl.com/api-reference/translate) On this page * [Change Notice](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#change-notice) * [Which cipher suites are being deprecated for the DeepL API?](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#which-cipher-suites-are-being-deprecated-for-the-deepl-api) * [Why is DeepL doing this now?](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#why-is-deepl-doing-this-now) * [What happens if a user continues to use a deprecated cipher suite?](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#what-happens-if-a-user-continues-to-use-a-deprecated-cipher-suite) * [What cipher suites will be supported after deprecation?](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#what-cipher-suites-will-be-supported-after-deprecation) * [What action should I take so that I’m not affected?](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#what-action-should-i-take-so-that-i%E2%80%99m-not-affected) * [How can I test my application after making changes to ensure I’m using a supported cipher suite?](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#how-can-i-test-my-application-after-making-changes-to-ensure-i%E2%80%99m-using-a-supported-cipher-suite) [](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#change-notice) Change Notice --------------------------------------------------------------------------------------------------------------------------------------------------------------- On or after July 29, 2024, DeepL will deprecate support for insecure cipher suites. Affected customers will need to upgrade their TLS library so that it doesn’t use a cipher suite that we’ll be deprecating. If you are using an insecure cipher suite and do not make this update, you’ll no longer be able to use the DeepL API from the deprecation date onward. Update on August 8, 2024: The deadline for this cipher deprecation has been extended to Monday, September 2, 2024.Please be sure to update your applications before September 2. We will not be able to extend the deadline any further. ### [](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#which-cipher-suites-are-being-deprecated-for-the-deepl-api) Which cipher suites are being deprecated for the DeepL API? On or after July 29, 2024, we will be deprecating the following three cipher suites: * TLS\_ECDHE\_RSA\_WITH\_AES\_256\_CBC\_SHA384 (0xc028) * TLS\_ECDHE\_RSA\_WITH\_AES\_256\_CBC\_SHA (0xc014) * TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA (0xc013) This means that any application with a TLS library: * That uses one of these cipher suites * _And_ does not support any of the cipher suites that will continue to be supported by DeepL …will no longer be able to connect to the DeepL API. ### [](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#why-is-deepl-doing-this-now) Why is DeepL doing this now? The cipher suites that we’re deprecating have a historical track record of security weaknesses. They’re still vulnerable to attacks that may enable a bad actor to decrypt data. We consider this to be an unacceptable security risk, especially given our commitment to keeping our customers’ data secure. After deprecating the ciphers listed above, the DeepL API will accept the same set of cipher suites supported by our web translator ([deepl.com](https://www.deepl.com/) ) today. ### [](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#what-happens-if-a-user-continues-to-use-a-deprecated-cipher-suite) What happens if a user continues to use a deprecated cipher suite? If you continue to use one of the cipher suites we’re deprecating, you won’t be able to access the DeepL API. This means that, for example, CAT tool plugins would no longer work properly. ### [](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#what-cipher-suites-will-be-supported-after-deprecation) What cipher suites will be supported after deprecation? We will continue to support the following cipher suites after deprecation: * TLS 1.3 (suites in server-preferred order) * TLS\_AES\_256\_GCM\_SHA384 (0x1302) * TLS\_CHACHA20\_POLY1305\_SHA256 (0x1303) * TLS\_AES\_128\_GCM\_SHA256 (0x1301) * TLS 1.2 (suites in server-preferred order) * TLS\_ECDHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384 * TLS\_ECDHE\_RSA\_WITH\_AES\_128\_GCM\_SHA256 ### [](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#what-action-should-i-take-so-that-i%E2%80%99m-not-affected) What action should I take so that I’m not affected? **If you’re a developer of your own application with the DeepL API:** * Ensure the TLS library you’re using supports one of the ciphers listed above If you’re using a third-party plugin that is powered by the DeepL API: * Update to the most recent version of the plugin Ask the plugin provider to upgrade their TLS library so that one of the cipher suites listed above is supported ### [](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites#how-can-i-test-my-application-after-making-changes-to-ensure-i%E2%80%99m-using-a-supported-cipher-suite) How can I test my application after making changes to ensure I’m using a supported cipher suite? September 2024 update: because the cipher deprecation has been carried out according to schedule, the endpoint below is obsolete and is no longer available for use. We created a test endpoint at `api-test-tls.deepl.com` that only supports the cipher suites that will still be available after the deprecation of insecure suites. You can send a test request to this endpoint to be sure that you’re using a supported cipher suite. If you receive a translation response back from the DeepL API, then you should not be affected by the deprecation. Below is an example cURL request using the test endpoint that Pro API users can use. Please remember to replace the `[yourAuthKey]` placeholder with your API key. Copy curl -X POST 'https://api-test-tls.deepl.com/v2/translate' \ --header "Authorization: DeepL-Auth-Key [yourAuthKey]" \ --header "Content-Type: application/json" \ --data \ '{ "target_lang": "DE", "text" : ["Hello, world!"] }' [Overview](https://developers.deepl.com/docs/resources/breaking-changes-change-notices) [March 2025: Deprecating GET requests to /translate and authenticating with auth\_key](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/march-2025-deprecating-get-requests-to-translate-and-authenticating-with-auth_key) ⌘I --- # November 2025: Deprecation of query parameter and request body authentication - DeepL Documentation [Skip to main content](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods#content-area) [Join the Developer Community on DeepL Bridges](https://dee.pl/7iwrt) [DeepL Documentation home page](https://developers.deepl.com/) Search... ⌘K Search... Navigation Breaking changes (change notices) November 2025: Deprecation of query parameter and request body authentication [Documentation](https://developers.deepl.com/docs/getting-started/intro) [API Reference](https://developers.deepl.com/api-reference/translate) On this page * [Change Notice](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods#change-notice) * [Why is DeepL doing this now?](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods#why-is-deepl-doing-this-now) * [What if I continue to use non-header authentication?](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods#what-if-i-continue-to-use-non-header-authentication) * [What action should I take so that I’m not affected?](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods#what-action-should-i-take-so-that-i%E2%80%99m-not-affected) [](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods#change-notice) Change Notice ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Update: The deadline for this deprecation has been extended to January 15th, 2026. On November 1st, 2025, DeepL will fully obsolesce support for providing authentication information in an `auth_key` query parameter or in an `auth_key` field of the request body. Deprecation of this feature was previously announced in [March 2025](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/march-2025-deprecating-get-requests-to-translate-and-authenticating-with-auth_key) , but we have continued to support it temporarily to allow more time for customers to complete the migration. You will no longer be able to authenticate a request to any endpoint by sending an API key in a query parameter or request body. Instead, send your API key in an HTTP header named `Authorization`. * **You will no longer be able to authenticate a request to any endpoint by sending an API key in a query parameter or in the request body.** Instead, send your API key in an HTTP header named `Authorization` . * **If you use one of DeepL’s officially-supported client libraries, you won’t be negatively affected by the breaking changes and do not need to update your application.** Specifically, we’ve confirmed the following client library versions: * [deepl-php](https://github.com/deeplcom/deepl-php) : 1.0.0+ * [deepl-python](https://github.com/deeplcom/deepl-python) : 1.0.0+ * [deepl-java](https://github.com/DeepLcom/deepl-java) : 1.0.0+ * [deepl-dotnet](https://github.com/DeepLcom/deepl-dotnet) : 1.0.0+ * [deepl-node](https://github.com/DeepLcom/deepl-node) : 1.1.0+ * [deepl-rb](https://github.com/DeepLcom/deepl-rb) : 3.0.0+ Going forward, you will need to authorize any API request, to any endpoint, by including your API key in an HTTP header named `Authorization`, like this: Copy Authorization: DeepL-Auth-Key [yourAuthKey] For detailed information on authorization and how to use the Authorization header, please see the [documentation](https://developers.deepl.com/docs/getting-started/auth) . Going forward, you will not be able to authorize any request, to any endpoint, by including your API key in an `auth_key` query parameter or an `auth_key` field of the request body. ### [](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods#why-is-deepl-doing-this-now) Why is DeepL doing this now? The API best practice is to authenticate a request by including the API key in an HTTP header. Sending an API key in a GET request or in a URL risks exposing the API key to the public via logs or other means. For privacy and security reasons, we must disallow this practice. ### [](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods#what-if-i-continue-to-use-non-header-authentication) What if I continue to use non-header authentication? After the date above, translation requests that attempt to authenticate with an `auth_key` query parameter or an `auth_key` field in the request body will fail with a `403 Forbidden` response. ### [](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods#what-action-should-i-take-so-that-i%E2%80%99m-not-affected) What action should I take so that I’m not affected? If you develop your own application using the DeepL API: * Ensure your code is not using either of the deprecated features. If you’re using a third-party plugin that is powered by the DeepL API: * Update to the most recent version of the plugin. If you experience trouble, contact the plugin provider to make sure they are aware of these deprecations. For further questions, please visit [our support page](https://support.deepl.com/) . [March 2025: Deprecating GET requests to /translate and authenticating with auth\_key](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/march-2025-deprecating-get-requests-to-translate-and-authenticating-with-auth_key) [Language release process](https://developers.deepl.com/docs/resources/language-release-process) ⌘I --- # Alpha and beta features - DeepL Documentation [Skip to main content](https://developers.deepl.com/docs/resources/alpha-and-beta-features#content-area) [Join the Developer Community on DeepL Bridges](https://dee.pl/7iwrt) [DeepL Documentation home page](https://developers.deepl.com/) Search... ⌘K Search... Navigation Resources Alpha and beta features [Documentation](https://developers.deepl.com/docs/getting-started/intro) [API Reference](https://developers.deepl.com/api-reference/translate) You might see API features in the documentation that are labeled as “alpha” or “beta”. You can find the official definition in our terms and conditions ([section 3.1.5](https://www.deepl.com/en/pro-license) ): > 3.1.5 DeepL is free to provide customers with additional functions in alpha or beta versions on a test basis (“Test Functions”). These Test Functions are marked as such or as alpha or beta. Test Functions are not the subject of this Agreement. DeepL may make them available voluntarily to all or individual customers and the Customer is not obliged to make any payment for the use of Test Functions. Test Functions are intended for test use by the Customer and evaluation by DeepL. They are not final products or features and may contain bugs or other inaccuracies. DeepL can change, adapt or discontinue the Test Functions at any time. In summary, features labeled as alpha or beta: * Are not intended to be used in production * Could be deprecated by DeepL at any time and without advance notice * Could be changed in a way that breaks API clients relying on them at any time and without advance notice Please keep this in mind when exploring or testing features labeled as alpha or beta. [Language release process](https://developers.deepl.com/docs/resources/language-release-process) [Open API spec](https://developers.deepl.com/docs/resources/open-api-spec) ⌘I --- # Breaking changes (Change Notices) - DeepL Documentation [Skip to main content](https://developers.deepl.com/docs/resources/breaking-changes-change-notices#content-area) [Join the Developer Community on DeepL Bridges](https://dee.pl/7iwrt) [DeepL Documentation home page](https://developers.deepl.com/) Search... ⌘K Search... Navigation Breaking changes (change notices) Breaking changes (Change Notices) [Documentation](https://developers.deepl.com/docs/getting-started/intro) [API Reference](https://developers.deepl.com/api-reference/translate) In this section, we’ll outline **planned deprecations and breaking changes** that might affect applications using the DeepL API. To learn about new releases, please see the [Release notes](https://developers.deepl.com/docs/resources/release-notes) page.[July 2024: Deprecation of insecure cipher suites\ ------------------------------------------------](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites) [March 2025: Deprecating GET requests to /translate and authenticating with auth\_key\ ------------------------------------------------------------------------------------](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/march-2025-deprecating-get-requests-to-translate-and-authenticating-with-auth_key) [November 2025: Deprecating query parameter and request body authentication\ --------------------------------------------------------------------------](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods) [Developer Community](https://developers.deepl.com/docs/resources/deepl-developer-community) [July 2024: Deprecation of insecure cipher suites](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/july-2024-deprecation-of-insecure-cipher-suites) ⌘I --- # XML handling - DeepL Documentation [Skip to main content](https://developers.deepl.com/docs/xml-and-html-handling/xml#content-area) [Join the Developer Community on DeepL Bridges](https://dee.pl/7iwrt) [DeepL Documentation home page](https://developers.deepl.com/) Search... ⌘K Search... Navigation XML and HTML handling XML handling [Documentation](https://developers.deepl.com/docs/getting-started/intro) [API Reference](https://developers.deepl.com/api-reference/translate) On this page * [Sentences with Markup](https://developers.deepl.com/docs/xml-and-html-handling/xml#sentences-with-markup) * [Ignored Tags](https://developers.deepl.com/docs/xml-and-html-handling/xml#ignored-tags) We’ve released [tag handling v2](https://developers.deepl.com/docs/xml-and-html-handling/tag-handling-v2) , providing major improvements to XML and HTML tag handling. Note that v2 enforces strict XML parsing. By default, the translation engine does not take tags into account. By setting the `tag_handling` parameter to `xml`, the API will process XML input by extracting the text out of the structure, splitting it into individual sentences, translating them, and placing them back into the XML structure. For best results, also set the [`tag_handling_version` parameter](https://developers.deepl.com/docs/xml-and-html-handling/tag-handling-v2) to `v2` in your request. For the translation of HTML content please see [HTML Handling](https://developers.deepl.com/docs/xml-and-html-handling/html) ### [](https://developers.deepl.com/docs/xml-and-html-handling/xml#sentences-with-markup) Sentences with Markup If you want to translate text where individual parts are marked up, you can simply activate the XML engine by setting `tag_handling` to `xml`. The following examples show marked-up text and how it will be translated: * Basic Example * With Attributes * Nested Tags * Placeholder Tag Request Copy Press Continue to advance to the next page. Response Copy Drücken Sie Weiter, um zur nächsten Seite zu gelangen. Request CopyThis is a premium feature.
Response CopyDies ist eine Premium-Funktion.
Parameters Copy tag_handling=xml, tag_handling_version=v2 Request Copy Press Continue to advance. Response Copy Drücken Sie „Weiter", um fortzufahren. Parameters Copy tag_handling=xml, tag_handling_version=v2 Request CopyThis tag is not closed properly Response (Error) Copy { "Message": "Tag handling parsing failed, please check input." } Only XML is strictly parsed. HTML is not strictly parsed. [](https://developers.deepl.com/docs/xml-and-html-handling/tag-handling-v2#compatibility) Compatibility ----------------------------------------------------------------------------------------------------------- Tag handling v2 is currently only compatible with the `quality_optimized` model type. Support for `latency_optimized` will be added in a future update. | Model Type | v1 Support | v2 Support | | --- | --- | --- | | `quality_optimized` | ✅ | ✅ | | `latency_optimized` | ✅ | ❌ | When you set `tag_handling_version` to `v2`, the `model_type` is implicitly set to `quality_optimized`. Requests that specify both `model_type=latency_optimized` and `tag_handling_version=v2` will return an error. [](https://developers.deepl.com/docs/xml-and-html-handling/tag-handling-v2#migration-guide) Migration Guide --------------------------------------------------------------------------------------------------------------- Tag handling is expected to give different results between v1 and v2. Thoroughly test your system and verify any differences in output before switching to v2 in production. ### [](https://developers.deepl.com/docs/xml-and-html-handling/tag-handling-v2#1-test-your-content) 1\. Test Your Content Run v2 translations on representative samples of your content, especially: * Text with deep tag hierarchies * Text with inline markup, attributes, and special characters * Edge cases such as empty or self-closing tags ### [](https://developers.deepl.com/docs/xml-and-html-handling/tag-handling-v2#2-compare-outputs) 2\. Compare Outputs Compare v1 and v2 outputs, and make any updates needed to maintain your workflows. * Ensure that the tags are preserved correctly * Compare any differences in translation * Note any formatting changes ### [](https://developers.deepl.com/docs/xml-and-html-handling/tag-handling-v2#3-validate-xml-syntax) 3\. Validate XML Syntax Since v2 enforces strict XML parsing: * Ensure all your XML input is well-formed * Add error handling for invalid XML responses * Update any XML generation logic if needed [](https://developers.deepl.com/docs/xml-and-html-handling/tag-handling-v2#related-documentation) Related Documentation --------------------------------------------------------------------------------------------------------------------------- For more information about XML and HTML tag handling: * [HTML Handling](https://developers.deepl.com/docs/xml-and-html-handling/html) * [XML Handling](https://developers.deepl.com/docs/xml-and-html-handling/xml) * [Structured XML Content](https://developers.deepl.com/docs/xml-and-html-handling/structured-content) [](https://developers.deepl.com/docs/xml-and-html-handling/tag-handling-v2#faq) FAQ --------------------------------------------------------------------------------------- **Q: What is the default tag handling version?** A: Customers who had not used tag handling prior to 2025-12-01 default to v2. All other customers default to v1. **Q: Should I upgrade to v2?** A: Upgrading to v2 is strongly recommended and will provide improvements to both translation quality and structural correctness. Test thoroughly with your specific content before switching in production. **Q: What happens if my XML is invalid?** A: Tag handling v2 enforces strict XML parsing. Invalid XML will return an error response. Ensure your XML is well-formed before submission. **Q: Can I switch back to v1 if needed?** A: Yes, simply set `tag_handling_version: v1` in your API requests. **Q: Does v2 work with all DeepL API features?** A: Tag handling v2 works with all standard API features including glossaries and formality settings. However, it currently only supports the `quality_optimized` model type. **Q: Is HTML also strictly parsed?** A: No, any HTML can be submitted for translation without throwing an error. Only XML is strictly parsed and requires valid XML. [HTML handling](https://developers.deepl.com/docs/xml-and-html-handling/html) [Roadmap and release notes](https://developers.deepl.com/docs/resources/roadmap-and-release-notes) ⌘I --- # Roadmap and release notes - DeepL Documentation [Skip to main content](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#content-area) [Join the Developer Community on DeepL Bridges](https://dee.pl/7iwrt) [DeepL Documentation home page](https://developers.deepl.com/) Search... ⌘K Search... Navigation Resources Roadmap and release notes [Documentation](https://developers.deepl.com/docs/getting-started/intro) [API Reference](https://developers.deepl.com/api-reference/translate) On this page * [In active development](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#in-active-development) * [February 2026](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#february-2026) * [January 2026](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#january-2026) * [2025](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#2025) * [2024](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#2024) * [2023](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#2023) * [2022](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#2022) [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#in-active-development) In active development * Add more events to audit logs for Pro API customers (API key management, cost control and usage limit changes) * Full CRUD functionality for managing [Style Rules](https://developers.deepl.com/api-reference/style-rules) and [Custom Instructions](https://developers.deepl.com/api-reference/translate/request-translation#body-custom-instructions) * Translation Memory via API * `v3/languages` endpoint with improved language code handling and additional functionality [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#february-2026) February 2026 [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#february-18-additional-languages-in-v2/languages) February 18 - Additional Languages in `v2/languages` ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- * New languages added to the [v2/languages endpoint](https://developers.deepl.com/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. [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#january-2026) January 2026 [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#january-20-legacy-auth-deprecation) January 20 - Legacy Auth Deprecation ----------------------------------------------------------------------------------------------------------------------------------------------------- Query parameter and request body authentication methods are now [deprecated](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods) . * **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. [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#january-8-81-new-languages-in-ga) 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](https://developers.deepl.com/docs/getting-started/supported-languages) for the complete language list. [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#2025) 2025 [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q4-2025) 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](https://developers.deepl.com/docs/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](https://developers.deepl.com/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](https://developers.deepl.com/docs/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](https://developers.deepl.com/api-reference/document) , currently in Beta. [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q3-2025) Q3 2025 --------------------------------------------------------------------------------------------- * Creation of an admin API, making it possible to manage API keys programmatically. See [here](https://developers.deepl.com/api-reference/admin-api) 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](https://developers.deepl.com/docs/getting-started/supported-languages) for more information. * Refreshed our API documentation and added new try-it explorers to support interacting with our APIs. See [here](https://developers.deepl.com/api-reference) to try it out! [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q2-2025) Q2 2025 --------------------------------------------------------------------------------------------- * Added support for new language: TH (Thai). For this release, this language will only support text translation. See [here](https://developers.deepl.com/docs/getting-started/supported-languages) 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](https://developers.deepl.com/docs/getting-started/supported-languages) for more information. * Added improvements to API glossaries, including the ability to edit glossaries and create multilingual glossaries. Learn more [here](https://developers.deepl.com/api-reference/multilingual-glossaries) . * Improvements to the `/usage` endpoint for Pro API customers ([API reference](https://developers.deepl.com/api-reference/usage-and-quota) ) * 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](https://developers.deepl.com/docs/getting-started/managing-api-keys#get-api-key-level-usage) . [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q1-2025) 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](https://developers.deepl.com/docs/getting-started/managing-api-keys#set-api-key-level-usage-limits) . * 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](https://developers.deepl.com/api-reference/improve-text) . [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#2024) 2024 [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q4-2024) 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](https://developers.deepl.com/api-reference/translate#about-the-model_type-parameter) . [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q3-2024) 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](https://developers.deepl.com/api-reference/translate#request-body-descriptions) . * 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](https://developers.deepl.com/docs/getting-started/supported-languages) . * An official Ruby client library, evolved from a community-written library by Daniel Herzog. You can download it [here](https://rubygems.org/gems/deepl-rb) or find the source code on our [GitHub page](https://github.com/DeepLcom/deepl-rb) . [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q2-2024) 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](https://github.com/DeepLcom/deepl-php?tab=readme-ov-file#document-minification) . * Added support for API key-level usage reporting. More information is available in the [multiple API keys guide](https://developers.deepl.com/multiple-api-keys#download-a-report-with-key-level-usage) . * Launched DeepL Pro in [165 new markets](https://www.deepl.com/en/blog/deepl-pro-expands-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](https://developers.deepl.com/docs/getting-started/alpha-and-beta-features) status to general availability. More information about the context parameter is available in the “Request body descriptions” table [here](https://developers.deepl.com/api-reference/translate) . * Added support for SRT (`srt`) files in [document translation](https://developers.deepl.com/api-reference/document) . [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q1-2024) 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](https://developers.deepl.com/multiple-api-keys) . * 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](https://developers.deepl.com/docs/getting-started/supported-languages) . * Added support for Korean (KO) as a [glossary](https://developers.deepl.com/api-reference/multilingual-glossaries) language, increasing the number of supported glossary language pairs from 55 to 66. [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#2023) 2023 [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q4-2023) Q4 2023 --------------------------------------------------------------------------------------------- * Added support for Microsoft Excel (`xlsx`) files in [document translation](https://developers.deepl.com/api-reference/document) . * Released the `context` parameter as an [alpha feature](https://developers.deepl.com/docs/getting-started/alpha-and-beta-features) for text translation (see [Request Body Descriptions table](https://developers.deepl.com/api-reference/translate#request-body-descriptions) for more information). [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q3-2023) Q3 2023 --------------------------------------------------------------------------------------------- * Launched DeepL Pro in South Korea ([blog post here](https://www.deepl.com/en/blog/deepl-pro-available-in-south-korea) ). This means users with billing addresses in South Korea can [create DeepL Pro API and Free API subscriptions](https://www.deepl.com/ko/pro#developer) . * Added support for Portuguese (PT), Russian (RU), and Chinese (ZH) as [glossary](https://developers.deepl.com/api-reference/multilingual-glossaries) 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 requires_`multipart/form-data`). [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q2-2023) Q2 2023 --------------------------------------------------------------------------------------------- * Added support for user-provided http clients in [PHP client library](https://github.com/DeepLcom/deepl-php) . * Released an official [DeepL API Postman collection](https://www.postman.com/deepl-api/workspace/deepl-api-developers/overview) . * Added formality support for Japanese (JA) in [text](https://developers.deepl.com/api-reference/translate) and [document](https://developers.deepl.com/api-reference/document) translation. * Released in-house PDF translation; removed requirement to send data to the US when translating PDF documents ([blog post](https://www.deepl.com/en/blog/deepl-launches-in-house-pdf-translation-for-improved-security-and-efficiency) ). [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q1-2023) Q1 2023 --------------------------------------------------------------------------------------------- * Released an official [DeepL Custom Connector](https://support.deepl.com/hc/en-us/articles/8644041855516-DeepL-API-custom-connector-for-Microsoft-Power-Automate) 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](https://developers.deepl.com/api-reference/document) 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](https://www.deepl.com/en/blog/welcome-korean-and-norwegian) . [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#2022) 2022 [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q4-2022) Q4 2022 --------------------------------------------------------------------------------------------- * Moved [HTML handling](https://developers.deepl.com/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](https://developers.deepl.com/api-reference/translate) , [usage](https://developers.deepl.com/api-reference/usage-and-quota) , and [languages](https://developers.deepl.com/api-reference/languages) endpoints. [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#q3-2022) Q3 2022 --------------------------------------------------------------------------------------------- * Released an official [PHP client library](https://github.com/DeepLcom/deepl-php) . * Added support for a new language for [text](https://developers.deepl.com/api-reference/translate) and [document](https://developers.deepl.com/api-reference/document) translation: UK (Ukrainian). [Blog post here](https://www.deepl.com/en/blog/deepl-learns-ukrainian) . [](https://developers.deepl.com/docs/resources/roadmap-and-release-notes#before-q3-2022) Before Q3 2022 ----------------------------------------------------------------------------------------------------------- * Released an official DeepL API [OpenAPI spec](https://github.com/DeepLcom/openapi) . * Released an official [NodeJS client library](https://github.com/DeepLcom/deepl-node) . * Released an official [.NET client library](https://github.com/DeepLcom/deepl-dotnet) . * Released an official [Python client library](https://github.com/DeepLcom/deepl-python) . * Added support for [glossaries](https://developers.deepl.com/api-reference/multilingual-glossaries) in the DeepL API. * Released an open-source sample project for [translating with DeepL in Google Sheets](https://github.com/DeepLcom/google-sheets-example) . * …and much more :) [New: XML/HTML handling v2](https://developers.deepl.com/docs/xml-and-html-handling/tag-handling-v2) [Usage and limits](https://developers.deepl.com/docs/resources/usage-limits) ⌘I --- # How to Use the Context Parameter Effectively - DeepL Documentation [Skip to main content](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#content-area) [Join the Developer Community on DeepL Bridges](https://dee.pl/7iwrt) [DeepL Documentation home page](https://developers.deepl.com/) Search... ⌘K Search... Navigation Guides How to Use the Context Parameter Effectively [Documentation](https://developers.deepl.com/docs/getting-started/intro) [API Reference](https://developers.deepl.com/api-reference/translate) On this page * [What the context parameter is for](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#what-the-context-parameter-is-for) * [What the context parameter is NOT for](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#what-the-context-parameter-is-not-for) * [How to use context for ambiguous words](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#how-to-use-context-for-ambiguous-words) * [Example](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#example) * [When to use this approach](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#when-to-use-this-approach) * [How to use context for grammatical gender](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#how-to-use-context-for-grammatical-gender) * [Example](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#example-2) * [When to use this approach](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#when-to-use-this-approach-2) * [How to use context for consistent name translation](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#how-to-use-context-for-consistent-name-translation) * [Example](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#example-3) * [When to use this approach](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#when-to-use-this-approach-3) * [Choosing the right feature for your needs](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#choosing-the-right-feature-for-your-needs) * [Technical details](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#technical-details) * [Cost](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#cost) * [Size limit](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#size-limit) * [Multi-text requests](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#multi-text-requests) * [Document translation](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#document-translation) * [Tag handling](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#tag-handling) * [Next steps](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#next-steps) **This guide shows you:** * When to use `context` (and when not to) * How to use `context` to resolve ambiguous words, genders, or transliterations * How to choose between `context`, Glossaries, and Style Rules * * * [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#what-the-context-parameter-is-for) What the context parameter is for ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The `context` parameter helps DeepL’s API translate ambiguous words and short text snippets more accurately by providing the surrounding content. Think of it like showing a human translator the paragraphs before and after the sentence being translated. The `context` parameter can help with: * Picking the correct translation for ambiguous words * Providing grammatical clues for gender, number, or case that isn’t clear from the text alone * Improving translations of short snippets such as headlines or product names [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#what-the-context-parameter-is-not-for) What the context parameter is NOT for --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- **Common Misconception:** Many users try to use `context` like ChatGPT system prompts. **This does not work reliably.** The `context` parameter is **not** designed for: * LLM-style instructions: “Translate with a friendly, casual tone” * Translation rules: “Always translate ‘Tor’ as ‘gate’” * Cultural context: “Adapt for German cultural norms” Using `context` like this will produce unpredictable results. The parameter is optimized for document content, not commands. Instead, try: * [Style rules and custom instructions](https://developers.deepl.com/api-reference/style-rules) : For tone, style, formatting, and translation instructions * [Glossaries](https://developers.deepl.com/api-reference/multilingual-glossaries) : For consistent terminology and brand names * * * [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#how-to-use-context-for-ambiguous-words) How to use context for ambiguous words ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- When a word has multiple meanings, surrounding context helps the translation engine choose the correct interpretation. ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#example) Example “Tor” could mean “gate” or “goal” in German. Without context, DeepL may not know which meaning you intend: Copy curl -X POST 'https://api.deepl.com/v2/translate' \ --header 'Authorization: DeepL-Auth-Key [your key]' \ --header 'Content-Type: application/json' \ --data '{ "text": [\ "Die Person stand vor dem Tor."\ ], "target_lang": "EN-US" }' **Output without context:** Copy "The person was standing in front of the gate." If you’re writing about a football game, provide context to clarify: Copy curl -X POST 'https://api.deepl.com/v2/translate' \ --header 'Authorization: DeepL-Auth-Key [your key]' \ --header 'Content-Type: application/json' \ --data '{ "text": [\ "Die Person stand vor dem Tor."\ ], "target_lang": "EN-US", "context": "Es war ein Fußballspiel." }' **Output with context:** Copy "The person was standing in front of the goal." ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#when-to-use-this-approach) When to use this approach * You’re translating short snippets that lack built-in context * The text contains words with multiple meanings * The surrounding content makes the intended meaning clear * * * [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#how-to-use-context-for-grammatical-gender) How to use context for grammatical gender ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- When grammatical gender isn’t clear from the source text, context can provide the necessary clues. ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#example-2) Example Without context, DeepL may not use the desired gender when translating: Copy curl -X POST 'https://api.deepl.com/v2/translate' \ --header 'Authorization: DeepL-Auth-Key [your key]' \ --header 'Content-Type: application/json' \ --data '{ "text": [\ "The teacher asked the class to tidy up after they finished the lesson."\ ], "target_lang": "DE" }' **Output without context:** (uses masculine form “Lehrer”) Copy "Der Lehrer bat die Klasse, nach der Stunde aufzuräumen." You can provide context from the surrounding text that clarifies the teacher’s gender: Copy curl -X POST 'https://api.deepl.com/v2/translate' \ --header 'Authorization: DeepL-Auth-Key [your key]' \ --header 'Content-Type: application/json' \ --data '{ "text": [\ "The teacher asked the class to tidy up after they finished the lesson."\ ], "target_lang": "DE", "context": "She did not want to tidy up herself." }' **Output with context:** (uses feminine form “Lehrerin”) Copy "Die Lehrerin bat die Klasse, nach der Stunde aufzuräumen." ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#when-to-use-this-approach-2) When to use this approach * Translating into languages with grammatical gender * The source text doesn’t specify gender * You have surrounding sentences that contain gender clues * * * [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#how-to-use-context-for-consistent-name-translation) How to use context for consistent name translation ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- When translating names in headlines or short snippets, the same name might be transliterated differently unless additional context is provided. ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#example-3) Example Content is not shared between `text` parameters. This results in different transliterations for the name “Sergej”. Copy curl -X POST 'https://api.deepl.com/v2/translate' \ --header 'Authorization: DeepL-Auth-Key [your key]' \ --header 'Content-Type: application/json' \ --data '{ "text": [\ "Sergej gibt Stellungnahme ab",\ "Sergej Zhivkov erklärte gestern, dass neue Maßnahmen ergriffen werden."\ ], "source_lang": "DE", "target_lang": "EN-US" }' **Output without context:** Copy { "translations": [\ {\ "detected_source_language": "DE",\ "text": "Sergej makes a statement"\ },\ {\ "detected_source_language": "DE",\ "text": "Sergei Zhivkov explained yesterday that new measures will be taken."\ }\ ] } Providing a longer snippet of `context` containing the complete name results in consistent transliteration: Copy curl -X POST 'https://api.deepl.com/v2/translate' \ --header 'Authorization: DeepL-Auth-Key [your key]' \ --header 'Content-Type: application/json' \ --data '{ "text": [\ "Sergej gibt Stellungnahme ab",\ "Sergej Zhivkov erklärte gestern, dass neue Maßnahmen ergriffen werden."\ ], "source_lang": "DE", "target_lang": "EN-US", "context": "Sergej Zhivkov erklärte gestern, dass neue Maßnahmen ergriffen werden." }' **Output with context:** Copy { "translations": [\ {\ "detected_source_language": "DE",\ "text": "Sergei issues statement"\ },\ {\ "detected_source_language": "DE",\ "text": "Sergei Zhivkov declared yesterday that new measures will be taken."\ }\ ] } ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#when-to-use-this-approach-3) When to use this approach * Translating news headlines separately from article bodies * Transliterating names with multiple possible spellings in your target language * * * [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#choosing-the-right-feature-for-your-needs) Choosing the right feature for your needs ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Different DeepL features solve different problems. Use this table to decide which best suits your use case. | Use Case | Context Parameter | Glossaries | Style Rules | | --- | --- | --- | --- | | **Ambiguous words** | ✅ | ❌ | ❌ | | **Consistent gender or spelling** | ✅ | ❌ | ❌ | | **Consistent domain-specific terminology** | ❌ | ✅ | ❌ | | **Brand names** | ❌ | ✅ | ❌ | | **Tone and style** | ❌ | ❌ | ✅ | | **Formatting rules** | ❌ | ❌ | ✅ | | **Translation instructions** | ❌ | ❌ | ✅ | * * * [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#technical-details) Technical details ----------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#cost) Cost Characters in the `context` parameter do not count toward billing. Only characters sent in the `text` parameter are billed. ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#size-limit) Size limit There is no size limit for the `context` parameter itself, but the request body size limit of 128 KiB applies to all text translation requests. ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#multi-text-requests) Multi-`text` requests Content is not shared between multiple `text` parameters sent in one request. Each text parameter is translated independently. In this example, “Tor” might be translated as “gate” instead of “goal” because the first `text` doesn’t have access to the second one’s content. Copy { "text": [\ "Die Person stand vor dem Tor.",\ "Es war ein Fußballspiel."\ ], "target_lang": "EN-US" } To ensure “Tor” is translated as “goal”, you can add additional sentences into the `context` parameter, or keep related content together in one `text` parameter. If you send a request with both `context` and multiple `text` parameters, the `context` parameter will be applied to each one. ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#document-translation) Document translation When using the [document translation endpoint](https://developers.deepl.com/api-reference/document) , the engine automatically uses the broader document context. You don’t need to provide explicit context for full documents. ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#tag-handling) Tag handling When using `tag_handling=xml` or `tag_handling=html`, tags are _not_ used as a context boundary. The translation engine automatically looks across all content provided in each `text` parameter. As with other types of texts, you may need to provide additional `context` when translating single tags without surrounding content. * * * [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter#next-steps) Next steps --------------------------------------------------------------------------------------------------------------------------------- Now that you understand the context parameter: * **Try it yourself:** Review the [text translation API reference](https://developers.deepl.com/api-reference/translate) for complete context parameter specifications * **Enforce terminology:** Learn how to use [glossaries](https://developers.deepl.com/api-reference/multilingual-glossaries) for consistent translations across all content * **Control style and tone:** Explore [style rules](https://developers.deepl.com/api-reference/style-rules) for formatting and tone instructions * **Translate full documents:** Understand how [document translation](https://developers.deepl.com/api-reference/document) automatically handles context [Making API calls from client-side JavaScript](https://developers.deepl.com/docs/learning-how-tos/cookbook/nodejs-proxy) [Mustache placeholder tags](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/placeholder-tags) ⌘I --- # DeepL MCP Server: How to build and use translation in LLM applications - DeepL Documentation [Skip to main content](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#content-area) [Join the Developer Community on DeepL Bridges](https://dee.pl/7iwrt) [DeepL Documentation home page](https://developers.deepl.com/) Search... ⌘K Search... Navigation Guides DeepL MCP Server: How to build and use translation in LLM applications [Documentation](https://developers.deepl.com/docs/getting-started/intro) [API Reference](https://developers.deepl.com/api-reference/translate) On this page * [What is MCP?](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#what-is-mcp) * [Setting Up Your DeepL MCP Server](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#setting-up-your-deepl-mcp-server) * [Prerequisites](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#prerequisites) * [Connecting to Claude Desktop](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#connecting-to-claude-desktop) * [Testing Your Server](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#testing-your-server) * [Understanding the Code](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#understanding-the-code) * [Server Initialization](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#server-initialization) * [Tool Definition](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#tool-definition) * [Transport Setup](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#transport-setup) * [Wrapping Up](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#wrapping-up) * [References](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#references) This cookbook is intended for developers who want to learn how to build an MCP server using the DeepL API. If you’re looking to simply use a pre-built DeepL MCP server without building it yourself, please go directly to the [GitHub repository](https://github.com/DeepLcom/deepl-mcp-server) for installation instructions. Large Language Models excel at many tasks but may not provide optimal translations for all languages. By combining the DeepL API with the Model Context Protocol (MCP), you can provide Claude and other MCP-compatible clients with access to DeepL’s specialized translation capabilities, bringing in the ability to provide translations across numerous languages. In this cookbook, we’ll explore how to create an MCP server that connects DeepL’s translation API with clients like Claude Desktop, GitHub Copilot, and any other clients that work with MCPs! This allows you to seamlessly translate text between languages within your conversations. To look at the code and start using it, go to [GitHub](https://github.com/DeepLcom/deepl-mcp-server) . ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#what-is-mcp) What is MCP? The Model Context Protocol (MCP) is an open standard introduced by Anthropic that standardizes how AI applications connect with external tools, data sources, and systems. Think of it as a “USB for AI integrations” – it provides a universal adapter between AI applications and external data sources through a standardized interface. This elegant design solves the integrations problem: instead of building custom connectors between each AI application and each external tool, developers only need to implement the MCP standard once on each side, reducing integration complexity. In the context of the DeepL MCP Server, MCP allows AI assistants to seamlessly access DeepL’s specialized translation capabilities while maintaining a consistent, secure communication protocol, combining the strengths of both systems to deliver a better User Experience. ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#setting-up-your-deepl-mcp-server) Setting Up Your DeepL MCP Server #### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#prerequisites) Prerequisites Before you begin, you’ll need: * A DeepL API key (get one at [DeepL API](https://www.deepl.com/pro-api) ) * Node.js installed on your system * Basic familiarity with JavaScript/Node.js 1 [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#) Initialize Your Project First, let’s set up a new Node.js project: Copy # Create a new directory for our project mkdir deepl-mcp-server cd deepl-mcp-server # Initialize npm project npm init -y # Install dependencies npm install @modelcontextprotocol/sdk deepl-node zod Here’s what each dependency does: * `@modelcontextprotocol/sdk`: The MCP SDK that allows our server to communicate with MCP clients like Claude Desktop * `deepl-node`: Official DeepL API client for Node.js, making it easy to interact with DeepL’s translation services * `zod`: A TypeScript-first schema validation library that we’ll use to define our tool parameters The Model Context Protocol (MCP) enables AI systems to access external tools, providing them with specialized capabilities beyond their built-in functionality. For translation tasks, this is particularly valuable as it combines DeepL’s translation expertise with Claude’s conversational abilities. 2 [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#) Create Your Server Implementation The `McpServer` class is the core of our implementation. It handles all the protocol-specific details of communicating with MCP clients. The `StdioServerTransport` uses standard input/output streams for communication, which works well with Claude Desktop’s execution model where it spawns separate processes for each server.We’re using environment variables to pass the DeepL API key to our server, which is a secure way to handle sensitive credentials. Create a file named `src/index.mjs` with the following structure: Copy import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js"; import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"; import { z } from "zod"; import * as deepl from 'deepl-node'; // The DeepL API Key is passed in as a part of the client configuration const DEEPL_API_KEY = process.env.DEEPL_API_KEY; const translator = new deepl.Translator(DEEPL_API_KEY); // Create server instance const server = new McpServer({ name: "deepl", // The name clients will use to identify this server version: "0.1.0-beta.0", // Version for compatibility checks capabilities: { resources: {}, tools: {}, }, }); // Server implementation goes here async function main() { const transport = new StdioServerTransport(); await server.connect(transport); console.error("DeepL MCP Server running on stdio"); } main().catch((error) => { console.error("Fatal error in main():", error); process.exit(1); }); 3 [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#) Implement DeepL API Helper Functions Let’s add some helper functions to manage language lists and validation. These helper functions serve several important purposes: 1. **Caching**: We cache the language lists to avoid unnecessary API calls, as these lists rarely change and DeepL has API usage limits. 2. **Validation**: Before sending requests to DeepL, we validate that the requested language codes are supported. This provides better error messages to users and prevents unnecessary API calls with invalid parameters. 3. **Separation of concerns**: By extracting these functions, we keep our tool implementations clean and focused on their primary purpose. The DeepL API distinguishes between source languages (languages you can translate from) and target languages (languages you can translate to), with slightly different sets of supported languages for each direction. Our implementation respects this distinction. Copy // Cache for language lists let sourceLanguagesCache = null; let targetLanguagesCache = null; // Helper function to validate languages async function validateLanguages(sourceLang, targetLang) { const sourceLanguages = await getSourceLanguages(); const targetLanguages = await getTargetLanguages(); if (sourceLang && !sourceLanguages.some(lang => lang.code === sourceLang)) { throw new Error(`Invalid source language: ${sourceLang}. Available languages: ${sourceLanguages.map(l => l.code).join(', ')}`); } if (!targetLanguages.some(lang => lang.code === targetLang)) { throw new Error(`Invalid target language: ${targetLang}. Available languages: ${targetLanguages.map(l => l.code).join(', ')}`); } } // Helper functions to get languages async function getSourceLanguages() { if (!sourceLanguagesCache) { sourceLanguagesCache = await translator.getSourceLanguages(); } return sourceLanguagesCache; } async function getTargetLanguages() { if (!targetLanguagesCache) { targetLanguagesCache = await translator.getTargetLanguages(); } return targetLanguagesCache; } 4 [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#) Define MCP Tools Let’s define one of the most important tools our server will provide - the translation tool. For brevity, we’ll only show one implementation, but the complete code includes additional tools like `get-source-languages`, `get-target-languages`, and `rephrase-text`. Copy server.tool( "translate-text", "Translate text to a target language using DeepL API", { text: z.string().describe("Text to translate"), sourceLang: z.string().nullable().describe("Source language code (e.g. 'en', 'de', null for auto-detection)"), targetLang: z.string().describe("Target language code (e.g. 'en-US', 'de', 'fr')"), formality: z.enum(['less', 'more', 'default', 'prefer_less', 'prefer_more']).optional().describe("Controls whether translations should lean toward informal or formal language"), }, async ({ text, sourceLang, targetLang, formality }) => { try { // Validate languages before translation await validateLanguages(sourceLang, targetLang); const result = await translator.translateText( text, sourceLang, targetLang, { formality } ); return { content: [\ {\ type: "text",\ text: result.text,\ },\ {\ type: "text",\ text: `Detected source language: ${result.detectedSourceLang}`,\ },\ ], }; } catch (error) { throw new Error(`Translation failed: ${error.message}`); } } ); For the complete implementation of all tools, including `get-source-languages`, `get-target-languages`, and `rephrase-text`, please refer to the [GitHub repository](https://github.com/DeepLcom/deepl-mcp-server) . ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#connecting-to-claude-desktop) Connecting to Claude Desktop To use your DeepL MCP server with Claude Desktop: 1. Create or edit the Claude Desktop configuration file: * On macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` * On Windows: `%AppData%\Claude\claude_desktop_config.json` * On Linux: `~/.config/Claude/claude_desktop_config.json` 2. Add your DeepL MCP server configuration: Copy { "mcpServers": { "deepl": { "command": "node", "args": [\ "/path/to/deepl-mcp-server/src/index.mjs"\ ], "env": { "DEEPL_API_KEY": "your-api-key-here" } } } } 3. Replace `/path/to/deepl-mcp-server` with the actual path to your server directory 4. Replace `your-api-key-here` with your actual DeepL API key 5. Restart Claude Desktop In case it worked, deepl should show up as one of the available tools within the “Search and Tools” menu.  ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#testing-your-server) Testing Your Server You can test your server’s capabilities by asking Claude Desktop translation-related questions: * “Can you translate ‘Hello, how are you?’ to German using DeepL?” * “Please translate this paragraph to Japanese using DeepL: \[your text here\]” * “Can you rephrase this text in a more formal way using DeepL: \[your text here\]” * “What languages can you translate from and to using DeepL?” Although it isn’t an exact science, mentioning the keyword “DeepL” helps Claude understand that we want to use that tool during the interaction.  ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#understanding-the-code) Understanding the Code Let’s break down the key components of our implementation: #### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#server-initialization) Server Initialization The `McpServer` class creates an MCP-compatible server that exposes tools to clients: Copy const server = new McpServer({ name: "deepl", version: "0.1.0-beta.0", capabilities: { resources: {}, tools: {}, }, }); #### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#tool-definition) Tool Definition Each tool follows a similar pattern: 1. Name of the tool 2. Description of what it does 3. Schema for parameters (using Zod) 4. Implementation function For example, the `translate-text` tool: Copy server.tool( "translate-text", // Name "Translate text using DeepL API", // Description { // Parameters schema text: z.string().describe("Text to translate"), // ...more parameters }, async ({ text, sourceLang, targetLang, formality }) => { // Implementation } ); #### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#transport-setup) Transport Setup The `StdioServerTransport` enables communication between the MCP server and clients: Copy const transport = new StdioServerTransport(); await server.connect(transport); ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#wrapping-up) Wrapping Up By following this cookbook, you’ve created an MCP server that enables Claude Desktop and other MCP-compatible clients to access DeepL’s translation capabilities. This allows seamless translation within your conversations, improving the multilingual capabilities of your AI interactions. As you expand your server, consider adding more features like: * Support for document translation * Custom glossaries for domain-specific terminology * Batch processing for multiple translations * Caching to improve performance and reduce API usage The combination of specialized AI services (like DeepL) with general-purpose AI assistants (like Claude) through MCP creates powerful workflows that combine the strengths of different AI systems. ### [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications#references) References [DeepL API](https://www.deepl.com/pro-api) [Model Context Protocol](https://modelcontextprotocol.io/) [DeepL MCP Server GitHub](https://github.com/DeepLcom/deepl-mcp-server) [Claude Desktop MCP Configuration](https://modelcontextprotocol.io/quickstart/server#testing-your-server-with-claude-for-desktop) [Glossaries in the real world](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/glossaries-in-the-real-world) [How to Translate Between Language Variants](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/translating-between-variants) ⌘I --- # Guides - DeepL Documentation [Skip to main content](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides#content-area) [Join the Developer Community on DeepL Bridges](https://dee.pl/7iwrt) [DeepL Documentation home page](https://developers.deepl.com/) Search... ⌘K Search... Navigation Guides [Documentation](https://developers.deepl.com/docs/getting-started/intro) [API Reference](https://developers.deepl.com/api-reference/translate) [Mustache placeholder tags\ -------------------------](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/placeholder-tags) [DeepL API 101\ -------------](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/first-things-to-try-with-the-deepl-api) [Glossaries in the real world\ ----------------------------](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/glossaries-in-the-real-world) [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications) [](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications) [DeepL MCP Server: How to Build and Use Translation in LLM Applications\ ----------------------------------------------------------------------](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications) [Written by](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/deepl-mcp-server-how-to-build-and-use-translation-in-llm-applications) [Akash Joshi](https://thewriting.dev/) [How to Use the Context Parameter Effectively\ --------------------------------------------](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/how-to-use-context-parameter) [How to Translate Between Language Variants\ ------------------------------------------](https://developers.deepl.com/docs/learning-how-tos/examples-and-guides/translating-between-variants) ⌘I ---