Search translation memory
Translation Memory
Search translation memory
Overview
- Runs an asynchronous TMX export based on wildcard/phrase queries and optional metadata filters. The job streams filtered translation units into TMX via the downstream
/export_tmx_by_queryendpoint. UsedownloadExport/{asyncRequestId}to fetch the finished file.
Flow
- Caller posts
ExportByQueryDto. - Service queues backend export (job metadata marks it asynchronous).
- Response contains
asyncRequest+asyncExportdescriptors so you can poll or receive callbacks.
Queries & locales
queriesalign one-to-one withqueryLangs. Each entry represents a search expression (supports*and?wildcards, max 5/10 respectively) applied to a locale.- Query semantics mirror the wildcard search endpoint: unquoted text = contains mode; quoted text = phrase mode; Boolean operators are ignored;
*or empty string means match-all (the backend may drop redundant source-only pairs). exportTargetLangssets which target TUVs are written to TMX. If omitted, all TM target locales are exported.
Filtering
- Timestamp bounds (
createdAtMin/Max,modifiedAtMin/Max) and author filters (createdBy,modifiedBy) narrow the TU set before export. - Optional
projectreference provides additional downstream scoping or naming context.
Output & limits
- Output is always TMX, streamed in chunks; filenames follow
dto.filenamewhen provided, otherwise backend defaults. - Requests with excessive locales or wildcard limit violations reject with
400. - If no matches remain after filtering, the job still produces an empty TMX.
Callbacks & polling
- Provide
callbackUrlto receive completion notification from the async mediator; otherwise pollasyncRequestvia standard async APIs and download through/downloadExport/{asyncRequestId}when ready.
POST
Search translation memory
Documentation Index
Fetch the complete documentation index at: https://developers.phrase.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Get a token from auth/login endpoint and then pass it in the Authorization HTTP header in every subsequent API call. For more information visit our help center.
Path Parameters
Body
application/json