Phrase Developer Hub

Docs, API reference, guides, and troubleshooting. Everything you need to run your localization workflow.

Why Phrase?

Keep your source strings in your codebase. Phrase ships every other language back into it, driven from the API, CLI, or your AI tools via MCP. Translation memory and term bases keep wording consistent and stop the same string from being paid for twice. No new place to manage strings, no loc pipeline to build or maintain.

Try it yourself

An end-to-end Strings API flow: project creation, language setup, machine translation (MT), and file download.

Set up project
Create locales
Upload file
Poll pre-translation status
Download translated file

One-time setup, also available in the Phrase Strings UI.

This creates the project with MT enabled. Copy the project id from the response, then create locales in a separate step.

See full reference Sign up

Before you start

Every request uses a short-lived JWT access token, passed as a Bearer token. You can generate an API token in Phrase Platform.

Read the authentication guide

One-time setup, also available in the Phrase Strings UI.

Create one locale per language. Set “default”: true on the source locale (en). Repeat for each target. Copy the target locale id from the response — you’ll need it for the download step.

See full reference Sign up

autotranslate=true triggers MT pre-translation of existing target locales. Must run after the target locale exists.

See full reference Sign up

Lists jobs newest first. Poll the first entry’s status: pending → running → success (or error, details in error). The upload returns before MT finishes, so keep polling until success.

See full reference Sign up

Explore Phrase APIs

APIs for managing localization at scale, from translating dynamic content to integrating with translation workflows.

Set up

Debug

Sync

Extend