> ## Documentation Index
> Fetch the complete documentation index at: https://developers.deepl.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Export a translation memory
> Learn how to export a translation memory as a TMX file, including how DeepL reuses recent exports and when it returns 409.
Exporting runs as a background job. This request starts the job and returns a `job_id`; the TMX file is downloaded separately once the job completes. TMX is currently the only export format, so there is no format parameter.
## Exporting a translation memory
```bash theme={null}
curl -X POST "https://api.deepl.com/v3/translation_memories/a74d88fb-ed2a-4943-a664-a4512398b994/export" \
-H "Authorization: DeepL-Auth-Key "
```
```json theme={null}
{
"job_id": "7c2e5a91-3b8d-4f16-8e0a-6d4c2b7f9a13",
"parameters": {
"translation_memory_id": "a74d88fb-ed2a-4943-a664-a4512398b994"
}
}
```
Check [the job](/api-reference/translation-memory/retrieve-a-translation-memory-job) until `status` is `completed`, then download the file from `download_url` on the job result.
```bash theme={null}
curl -X GET "https://api.deepl.com/v3/translation_memories/jobs/7c2e5a91-3b8d-4f16-8e0a-6d4c2b7f9a13" \
-H "Authorization: DeepL-Auth-Key "
```
```json theme={null}
{
"job_id": "7c2e5a91-3b8d-4f16-8e0a-6d4c2b7f9a13",
"product": "translation_memory",
"operation": "export",
"creation_time": "2026-08-06T15:04:25.223Z",
"updated_time": "2026-08-06T15:05:02.771Z",
"parameters": {
"translation_memory_id": "a74d88fb-ed2a-4943-a664-a4512398b994"
},
"results": [
{
"status": "completed",
"download_url": "https://assets.deepl.com/download/7c2e5a91-3b8d-4f16-8e0a-6d4c2b7f9a13",
"expires_at": "2026-08-06T16:05:02.771Z"
}
]
}
```
## Handling 200, 202, and 409
The status code tells you whether a new job was started:
| **Status** | **Meaning** | **What to do** |
| -------------- | ------------------------------------------------------- | ------------------------------------------------------ |
| `202 Accepted` | A new export job was started | Poll `job_id` |
| `200 OK` | A recent export was still available and was reused | Poll `job_id` |
| `409 Conflict` | An export of this translation memory is already running | Poll the job you already have; do not retry the export |
Treat `200` and `202` the same way. Both return a usable `job_id`, and the only difference is whether DeepL did the work again.
Do not retry on `409`. Retrying will keep conflicting with the in-progress export. Poll the `job_id` from your earlier request instead, and hold onto that ID so you can recover without a retry loop.
`download_url` is short-lived and stops working at `expires_at`. Download the file when the job completes rather than storing the URL for later. If the URL has expired, start a new export.
## OpenAPI
````yaml post /v3/translation_memories/{translation_memory_id}/export
openapi: 3.0.3
info:
title: DeepL API Documentation
description: >-
The DeepL API provides programmatic access to DeepL’s language AI
technology.
Note: this OpenAPI spec is embedded into our API documentation and has
shortened descriptions.
termsOfService: https://www.deepl.com/pro-license
contact:
name: DeepL - Contact us
url: https://www.deepl.com/contact-us
version: 3.12.0
servers:
- url: https://api.deepl.com
description: DeepL API Pro
- url: https://api-free.deepl.com
description: DeepL API Free
security: []
tags:
- name: beta
description: >-
Experimental features that are under testing and not yet intended for
production use.
- name: TranslateText
description: >-
The text-translation API currently consists of a single endpoint,
`translate`, which is described below.
- name: TranslateDocuments
description: >-
The document translation API allows you to translate whole documents and
supports the following file types and extensions:
* `docx` - Microsoft Word Document
* `pptx` - Microsoft PowerPoint Document
* `xlsx` - Microsoft Excel Document
* `pdf` - Portable Document Format
* `htm / html` - HTML Document
* `txt` - Plain Text Document
* `xlf / xliff` - XLIFF Document (versions 1.2, 2.0, and 2.1)
* `srt` - SRT Document
* `idml` - Adobe InDesign Markup Language
* `xml` - XML Document
* `json` - JSON Document
* `dita` - DITA topic (Darwin Information Typing Architecture)
* `mif` - Adobe FrameMaker Interchange Format
* `jpeg` / `jpg` / `png` - Image (currently in beta)
- name: RephraseText
description: >-
The `rephrase` endpoint is used to make corrections and adjustments to
texts based on style or tone.
- name: CorrectText
description: >-
The `correct` endpoint fixes spelling and grammar errors without broader
rephrasing. Use it when you want
a minimal-change correction pass rather than the broader rewriting
performed by `rephrase`.
- name: ManageSpokenTerms
description: >-
The *Spoken Terms* functions allow you to create, inspect, edit and delete
Spoken Terms collections.
Spoken Terms improve speech recognition in the Voice API: they ensure
specific words and phrases,
such as company names, acronyms, and product names, are transcribed
correctly. A collection contains
one or more term lists, each holding terms for a single language, and is
applied to a voice session
via the `spoken_terms_id` parameter.
- name: ManageMultilingualGlossaries
description: >-
The *glossary* functions allow you to create, inspect, edit and delete
glossaries.
Glossaries created with the glossary function can be used in translate
requests by specifying the
`glossary_id` parameter. A glossary contains (several) dictionaries.
A dictionary is a mapping of source phrases to target phrases for a single
language pair.
If you encounter issues, please let us know at support@DeepL.com.
Currently you can create glossaries with any of the languages DeepL
supports (with the exception of Thai).
The maximum size limit for a glossary is 10 MiB = 10485760 bytes and each
source/target text,
as well as the name of the glossary, is limited to 1024 UTF-8 bytes.
A total of 1000 glossaries are allowed per account.
When creating a dictionary with target language `EN`, `PT`, or `ZH`, it's
not necessary to specify a variant
(e.g. `EN-US`, `EN-GB`, `PT-PT`, `PT-BR`, or `ZH-HANS`).
Dictionaries with target language `EN` can be used in translations with
either English variant.
Similarly `PT`, and `ZH` dictionaries can be used in translations with
their corresponding variants.
(When you provide the ID of a glossary to a translation, the appropriate
dictionary is automatically applied. Currently glossaries can not yet be
used with source language detection.)
Glossaries created via the DeepL API are now unified with glossaries
created via the DeepL website and DeepL apps.
Please only use the v3 glossary API in conjunction with multilingual or
edited glossaries from the website.
- name: ManageGlossaries
description: >-
Please note that this is the spec for the (old) v2 glossary endpoint.
We recommend users switch to the newer v3 glossary endpoints, which
support editability and multilinguality.
The *glossary* functions allow you to create, inspect, and delete
glossaries.
Glossaries created with the glossary function can be used in translate
requests by specifying the
`glossary_id` parameter.
If you encounter issues, please let us know at support@DeepL.com.
Currently you can create glossaries with any of the languages DeepL
supports (with the exception of Thai).
- name: MetaInformation
description: Information about API usage and value ranges
- name: TranslationMemories
description: >-
The translation memory endpoints allow you to manage your account's
translation memories, used to store
and reuse previously created translations. You can list and retrieve
translation memories, page through
their stored segments, create one by importing a TMX file, export one back
to TMX, and delete one.
Editing the contents of an existing translation memory is not supported;
import a new one instead.
Importing and exporting run as background jobs. Create the job, then poll
`GET /v3/translation_memories/jobs/{job_id}` until it reports `completed`.
Translation memories can be used in text translation requests by
specifying the `translation_memory_id` parameter to denote a specific
translation memory and the
`translation_memory_threshold` which defines the minimum matching
percentage required for a translation memory
segment to be applied (recommended to be 75% or higher). A translation
request fails with `404` if the
translation memory does not exist or does not cover the requested language
pair.
- name: VoiceAPI
description: >-
The Voice API provides real-time voice transcription and translation
services.
Use a two-step flow: first request a streaming URL via REST, then
establish a WebSocket connection for streaming audio and receiving
transcriptions.
- name: VoiceTranslateJob
description: >-
**Alpha.** Async voice translation jobs. This API may change without
notice.
- name: AdminApi
description: >-
Endpoints for organization administrators to manage API keys and retrieve
usage analytics.
- name: QualityEvaluation
description: >-
**Closed alpha.** Evaluate translation quality. Submit source/target
segment pairs and retrieve per-segment quality issues categorized by error
type and severity, with character spans pointing to where each issue
occurs.
externalDocs:
description: DeepL Pro - Plans and pricing
url: https://www.deepl.com/pro#developer
paths:
/v3/translation_memories/{translation_memory_id}/export:
post:
tags:
- TranslationMemories
summary: Export a translation memory
description: >-
Export a translation memory as a TMX file.
The export runs as a background job. Poll
[Retrieve an import or export
job](/api-reference/translation-memory/retrieve-a-translation-memory-job)
until the status is `completed`, then download the file from the
`download_url` on the job result.
That URL is short-lived, so download the file rather than storing the
link.
If a recent export of the same translation memory is still available,
DeepL reuses it and returns
`200 OK` with that job instead of starting a new one. Handle both `200`
and `202` as success. If a
different export of the same translation memory is still running, the
request returns
`409 Conflict`.
Requires an API key with the `translation_memories:read` scope.
operationId: createTranslationMemoryExport
parameters:
- name: translation_memory_id
in: path
required: true
schema:
$ref: '#/components/schemas/TranslationMemoryId'
description: The ID of the translation memory to export.
responses:
'200':
description: >-
An existing export was reused. Poll the returned `job_id` for the
download URL.
headers:
X-Trace-ID:
$ref: '#/components/headers/X-Trace-ID'
content:
application/json:
schema:
$ref: '#/components/schemas/CreateTranslationMemoryExport'
examples:
Basic:
value:
job_id: 7c2e5a91-3b8d-4f16-8e0a-6d4c2b7f9a13
parameters:
translation_memory_id: a74d88fb-ed2a-4943-a664-a4512398b994
'202':
description: >-
The export job was created. Poll the returned `job_id` for the
download URL.
headers:
X-Trace-ID:
$ref: '#/components/headers/X-Trace-ID'
content:
application/json:
schema:
$ref: '#/components/schemas/CreateTranslationMemoryExport'
examples:
Basic:
value:
job_id: 7c2e5a91-3b8d-4f16-8e0a-6d4c2b7f9a13
parameters:
translation_memory_id: a74d88fb-ed2a-4943-a664-a4512398b994
'400':
$ref: '#/components/responses/BadRequest'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/ForbiddenScoped'
'404':
description: >-
The translation memory could not be found. This is also returned for
a translation memory that
belongs to another account.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
'409':
description: >-
An export of this translation memory is already in progress. Poll
that job instead of starting
another export.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
'429':
$ref: '#/components/responses/TooManyRequests'
'500':
$ref: '#/components/responses/InternalServerError'
'503':
$ref: '#/components/responses/ServiceUnavailable'
security:
- auth_header: []
components:
schemas:
TranslationMemoryId:
type: string
format: uuid
description: A unique ID assigned to a translation memory.
example: a74d88fb-ed2a-4943-a664-a4512398b994
CreateTranslationMemoryExport:
description: A reference to a translation memory export job.
type: object
required:
- job_id
- parameters
properties:
job_id:
description: The identifier of the export job. Use it to poll the job's status.
type: string
format: uuid
example: 7c2e5a91-3b8d-4f16-8e0a-6d4c2b7f9a13
parameters:
type: object
properties:
translation_memory_id:
$ref: '#/components/schemas/TranslationMemoryId'
ErrorResponse:
type: object
required:
- message
properties:
message:
type: string
description: A human-readable description of the error.
code:
type: string
description: >-
A machine-readable identifier for the error, when available. Clients
should match on this value rather than on `message` when branching
on error types.
example: invalid_content_type
headers:
X-Trace-ID:
description: >-
A unique identifier for the request that can be included in bug reports
to DeepL support.
schema:
type: string
example: 501c3d93cc0c4f11ae2f60a226c2f0f0
responses:
BadRequest:
description: Bad request. Please check error message and your parameters.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
Unauthorized:
description: >-
Authorization failed. Please supply a valid `DeepL-Auth-Key` via the
`Authorization` header.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
ForbiddenScoped:
description: >-
Authorization failed. Please supply a valid `DeepL-Auth-Key` via the
`Authorization` header. This error is also returned when the API key is
scoped but does not include the scope required for this endpoint.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
TooManyRequests:
description: Too many requests. Please wait and resend your request.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
InternalServerError:
description: Internal error.
ServiceUnavailable:
description: Resource currently unavailable. Try again later.
securitySchemes:
auth_header:
type: apiKey
description: >
Authentication with `Authorization` header and `DeepL-Auth-Key`
authentication scheme. Example: `DeepL-Auth-Key `
name: Authorization
in: header
x-default: 'DeepL-Auth-Key '
````