Manual
Overview Getting Started Core concepts Quick Start Guide Create an account and sign in Projects Create and manage projects Project settings Languages Workflow and translation lock Translation Keys Key names and groups ICU messages and placeholders Translating The translation editor Keyboard shortcuts Review & Reports Review workflow Reports Branches & Merging Branch workflows: create, merge, and delete The Branches page Translation Memory How translation memory works Glossary The glossary Import & Export Import and export files File formats Integrations GitHub GitLab CI and CLI settings Webhooks Teams & Access Roles and permissions Teams Inviting people Project access Account & Organization Account settings Organization settings Billing & Plans Plans and limits
CLI
Overview Set up the CLI Commands File formats Use the CLI in CI
API
Overview Authentication: API keys and session tokens Endpoints Pull translations for your build
Log in Get started free
API

Pull translations for your build

Get the approved translations of a project into your build pipeline.

1 min read ยท Updated October 2026

Use the pull route to get translations into a build:

HTTP 
GET https://api.continuous-translations.com/projects/{id}/pull?language=nl&branch=main
Authorization: Bearer <YOUR_API_KEY>
ParameterDescription
languageThe language code, e.g. nl
branchThe branch to read, e.g. main
statusWhich translations to include. The CLI asks for approved translations unless you pass --drafts

The key needs the translations:read scope, see Authentication.

Let the CLI do it #

For most projects you don’t call this route yourself. ct pull calls it for every active language and writes the files in your project’s format:

SH 
npx @continuous-translations/cli pull

See Commands for options such as --require-complete 100, and Use the CLI in CI for pipeline examples.

Automate it #

Start a build with a webhook when all keys on a branch reach 100% translation coverage. This is the recommended pattern for continuous deployment.