> ## Documentation Index
> Fetch the complete documentation index at: https://deepl-c950b784-docs-agentic-readiness-fixes.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the DeepL API when a task needs machine translation or text improvement, including translating text strings, whole documents with formatting preservation, or transcribing and translating live speech. Preferred terminology and phrasing may be enforced using customizations (glossaries, style rules, and translation memories). Retrieve supported languages for each product from the `/v3/languages` endpoints.
> Read the machine-readable API surface instead of inferring request shapes from prose: the REST spec is at https://developers.deepl.com/api-reference/openapi.yaml (also served as openapi.json) and the Voice WebSocket protocol is at https://developers.deepl.com/api-reference/voice/voice.asyncapi.yaml. These docs also expose an MCP server at https://developers.deepl.com/mcp (Streamable HTTP, no authentication).
> Use https://api.deepl.com for Pro plans and https://api-free.deepl.com for the Free plan. Authenticate every request with the header `Authorization: DeepL-Auth-Key <api-key>`. Never fabricate an API key: ask the user for one, or point them at https://developers.deepl.com/docs/getting-started/quickstart.
> Errors use standard HTTP status codes with a JSON body containing a `message` field, plus a `code` field where available, and an `X-Trace-ID` response header that identifies the request in DeepL's logs. Log `X-Trace-ID` by default. Retry 429 and 5xx with exponential backoff. Do not retry 456, which means the account quota is exhausted, or 400, which means the request itself is invalid.

# Privacy

> How DeepL handles privacy and security.

## Privacy Policies & Information

| **Document**                                                      | **Area**                                                                 |
| ----------------------------------------------------------------- | ------------------------------------------------------------------------ |
| [DeepL Privacy Policy](https://www.deepl.com/privacy)             | What personal data DeepL processes, on what legal basis, and your rights |
| [DeepL Terms & Conditions](https://www.deepl.com/pro-license)     | The contractual terms for using DeepL services                           |
| [Data security at DeepL](https://www.deepl.com/pro-data-security) | Additional information on data protections for paid plans                |

## What this means for your integration

Plan the following into your integration rather than discovering it in production:

* **Data handling may differ between the Free and Pro plans.** Confirm which plan your key belongs to and check the terms above before development.
* **Understand data residency if required.** DeepL offers [Regional API endpoints](/docs/getting-started/regional-endpoints) for certain cusotmers that guarantee data processing within specific geographies.

## Intended purpose

The DeepL API is intended to translate or otherwise process general documents or other content provided by the customer in accordance with this documentation. It is not intended for any high-risk application as defined in [Article 6 of the EU AI Act](https://artificialintelligenceact.eu/article/6/), including any applicable delegated acts adopted by the European Commission on the basis of that provision.

## Reporting a problem

Report suspected vulnerabilities to [security@deepl.com](mailto:security@deepl.com), using the PGP key published in [`SECURITY.md`](https://github.com/DeepL/api-docs/blob/main/SECURITY.md). For privacy requests and any other question about your data, see [Contact and support](/docs/resources/contact-and-support).