Download a previously generated TMX export
Changed onDownloads 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.
- 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.
- 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.
- 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.
Request
- Base URLhttps://api.smartling.com
- AuthHTTP bearer
Path parameters
The account’s unique identifier. This can be found in the Smartling Dashboard under Account Settings > API.
Opaque, base64-encoded key identifying a previously generated TMX export (an export job UID and version, encoded together). Treat as an opaque token; do not construct or parse it manually.
Response
The TMX file content.
Changes
- info
endpoint added
- info