---
title: "Download a previously generated TMX export"
method: GET
path: "/tm-tmx-api/v2/accounts/{accountUid}/tmx/file/{tmxFileKey}"
tags: ["Translation Memory"]
---

# Download a previously generated TMX export

`GET /tm-tmx-api/v2/accounts/{accountUid}/tmx/file/{tmxFileKey}`

## Request

- Base URL: `https://api.smartling.com`
- URL: `https://api.smartling.com/tm-tmx-api/v2/accounts/{accountUid}/tmx/file/{tmxFileKey}`
- Auth: HTTP bearer

Downloads a TMX file previously generated by exporting a translation memory. You can generate the export in one of two ways.

- **From the dashboard.** See <a href="https://help.smartling.com/hc/en-us/articles/360008268793-Translation-Memory-Management#h_01EYJX88ZXJ3M9PNWBDS6ZBRSX" target="_blank" rel="noopener noreferrer">Export a TM</a>. Smartling emails you a download link once the export completes.
- **Via the Translation Memory GraphQL API**, if you want to trigger the export from your own integration instead of the dashboard.
  1. Call <a href="https://graphql-reference.smartling.com/tm-graphql-api/#mutation-createStringSearch" target="_blank" rel="noopener noreferrer">createStringSearch</a> to define which TM strings to export. This returns a `searchUid`.
  2. Call <a href="https://graphql-reference.smartling.com/tm-graphql-api/#mutation-bulkExportTmStrings" target="_blank" rel="noopener noreferrer">bulkExportTmStrings</a> with that `searchUid` to start the export. This returns an `actionUid`.
  3. Poll <a href="https://graphql-reference.smartling.com/tm-graphql-api/#query-bulkExportTmStringsStatus" target="_blank" rel="noopener noreferrer">bulkExportTmStringsStatus</a> with the `actionUid` until `executionComplete` is `true`. The response includes a `tmxDownloadKey`.

Whichever method you use, this endpoint is the last step. It retrieves the generated file. The `tmxFileKey` parameter is the opaque key returned by the export.

- If you generated the export from the dashboard, this key comes from the download link in the completion email.
- If you generated the export via the GraphQL API, this key is the `tmxDownloadKey` value returned by `bulkExportTmStringsStatus`.

The key is scoped to `accountUid`. A key from another account's export cannot be used here.

Export files expire 14 days after generation. After expiry, the export must be regenerated.

## Path parameters

- `accountUid` string, required
- `tmxFileKey` string, required

## Response `200`

The TMX file content.

## Other responses

- `401`: Provided credentials are not valid.
- `403`: Caller does not have access to the requested resource.
- `404`: No TMX export matches `tmxFileKey` for this `accountUid`.
- `410`: The export's underlying file has expired and must be regenerated.
- `500`: Unexpected error

## Changes

- **2026-10-17** `2cd7a8215799`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/smartling/apis/smartling-rest-api-reference/changes/tm-tmx-api/v2/accounts/:accountUid/tmx/file/:tmxFileKey/get.md)

---

[API](https://skmtc.dev/smartling/apis/smartling-rest-api-reference.md) - [All operations](https://skmtc.dev/smartling/apis/smartling-rest-api-reference/llms.txt) - [OpenAPI document](https://skmtc.dev/smartling/apis/smartling-rest-api-reference/revisions/e63066e7f5e9?raw)