Skip to main content
In the wrong place? Looking for a specific endpoint’s request and response schema? That lives in the API Reference, not here. This page is for deciding which API to call, not how a single endpoint behaves.

​
How Strings and TMS fit together

Most builders start in one of two places, and it comes down to who owns the source. If a developer owns it (source strings in an app or repository), reach for Strings. If a content or localization team owns it (documents, marketing, web content), reach for TMS. The two connect through Job Sync, so a mixed org can use both without splitting systems. Everything else on this page extends one of those two.

​
First call: authenticate

Every Phrase API uses the same authorization model: generate an API token, exchange it for a short-lived access token, and send that as a Bearer token on every request. For automation, use a Service Account instead of a personal token. Full setup, regional endpoints, and Service Account scopes are in the Platform Authentication guide. Every section below assumes a valid access token.

​
Choose your API

Match your task to a goal below, then use the suggested API.

FOUNDATION

LOCALIZE YOUR SOFTWARE

LOCALIZE CONTENT AT SCALE

TRANSLATE AND CHECK WITH AI

DEFINE REUSABLE RULES

CONNECT AND EXTEND

​
Common pain points, and where each is handled

​
Next steps

  1. New to Phrase: authenticate with the token exchange above, then push a locale file with the Strings CLI.
  2. Building an automation: set up a Service Account so the integration does not depend on a personal token.
  3. Extending TMS: start with the Build a TMS plugin guide.
  4. Track changes: subscribe to the Changelog.
Last updated: September 7, 2026. Track documentation changes in the changelog.