Sync locale files and manage translation keys programmatically for a software product with the Phrase Strings API
domain: developers.phrase.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with a Phrase access token and identify the target project ID
Push source content by uploading a locale file (POST uploads) specifying file format, locale, and tag options
Poll the upload's associated background job/summary to confirm keys/translations were created without conflicts
Pull translations by downloading a locale file (GET locales/{id}/download) in the target format for a given locale, or use the CLI wrapper over the same endpoints
Manage locales and branches directly via the locales/branches endpoints when supporting multi-version releases
Known gotchas
Phrase Strings (key-based, software localization) and Phrase TMS (workflow/job-based, formerly Memsource) are different products with separate API surfaces — Strings API calls will not manage TMS jobs or vice versa
Uploads that don't specify the correct file format/tag options can silently misparse placeholders or pluralization syntax, corrupting keys on import
Downloading a locale file returns a snapshot at request time; concurrent edits during a long-running pipeline can produce a stale export
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?