Localizely API

Name: Localizely API API
Brand: Localizely API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationapiKey4 EndpointsREST

For Agents

Upload and download localization files, create branches, and check translation status against a Localizely project from CI or agent workflows.

Quickstart

Get started with Localizely API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"download translated localization files"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Localizely API API.

Upload localization files into a Localizely project for translation

Download translated files in the source format for build-time consumption

Create a branch in a project to isolate work-in-progress translations

Check the translation status of a project to gate releases on completion

GET STARTED

Start building with Localizely API API

Explore with Jentic

View OpenAPI Document

Use for: Upload a JSON localization file to my Localizely project, Download the latest translated files for a release build, Create a feature branch in my Localizely project, Check whether all languages in this project are 100% translated

Not supported: Does not handle machine translation, key-level CRUD, or in-app translation rendering — use for project file upload, download, and translation status only.

Jentic publishes the only available OpenAPI document for Localizely API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Localizely API, keeping it validated and agent-ready. Localizely is a translation management platform built around uploading and downloading localization files, with branch and project organisation. The API is intentionally narrow: it covers file upload, file download, branch creation, and translation status checks, designed to be wired into curl scripts and CI pipelines that move translation files in and out of the platform. Authentication is by per-account API token in the X-Api-Token header.

Use Cases

Patterns agents use Localizely API API for, with concrete tasks.

★ Translation File CI Pipeline

Engineering teams that ship localised apps want translations pulled into the build at CI time. Localizely's download endpoint returns the latest translation file in the source format, and the status endpoint exposes per-language completion. A CI step calls download for each release and optionally fails the build if a key language is below threshold.

Call GET /v1/projects/{project_id}/files/download for each language in the build, check GET /v1/projects/{project_id}/status, and fail if completion is below the configured threshold.

Source String Upload from Source Control

When developers add new strings to the codebase, those strings need to land in Localizely so translators can pick them up. POST /v1/projects/{project_id}/files/upload accepts the source localization file. Combined with the branch endpoint, teams can isolate new strings on a feature branch until they are ready for production translators.

Call POST /v1/projects/{project_id}/branches/{branch} to create a feature branch then POST /v1/projects/{project_id}/files/upload with the new source strings.

AI Agent Release Gate

An AI agent running release checks can call Localizely through Jentic to confirm translations are complete before approving a deployment. The agent searches Jentic for the status operation, executes it with the project ID, and reports back per-language completion. The API token stays in the Jentic vault.

Use Jentic to call GET /v1/projects/{project_id}/status and report any language below 95% complete to the deployment workflow.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for localizely api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/projects/{project_id}/files/upload

Upload a localization file

GET

/v1/projects/{project_id}/files/download

Download translated files

POST

/v1/projects/{project_id}/branches/{branch}

Create a project branch

GET

/v1/projects/{project_id}/status

Get translation completion status

POST

/v1/projects/{project_id}/files/upload

Upload a localization file

GET

/v1/projects/{project_id}/files/download

Download translated files

POST

/v1/projects/{project_id}/branches/{branch}

Create a project branch

GET

/v1/projects/{project_id}/status

Get translation completion status

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Localizely admin tokens are stored encrypted in the Jentic vault. The X-Api-Token header is injected at execution time, so the raw token never enters agent context, logs, or LLM traces.

Intent-based discovery

Agents search Jentic for intents like 'download translated files' or 'check translation status' and Jentic returns the matching Localizely operation with its input schema, so the agent can run release checks without consulting documentation.

Time to first call

Direct Localizely integration: half a day for auth, file upload and download, and status polling in a CI job. Through Jentic: under 30 minutes to search, load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Phrase API

Alternative translation management platform with a deeper API surface beyond file upload and download

Choose Phrase when the team needs CRUD on individual keys, advanced workflow controls, or deep integrations beyond Localizely's file-centric API.

Alternative

POEditor API

Alternative file-based translation management platform with similar upload and export operations

Choose POEditor when the workflow centres on collaborative crowdsourced translation rather than Localizely's branch-and-CI model.

Alternative

Smartling API

Alternative enterprise translation management platform with managed translation services

Choose Smartling when the user needs human translation services bundled with the platform rather than just file in/out and status.

FAQs

Specific to using Localizely API API through Jentic.

Why is there no official OpenAPI spec for Localizely API?

Localizely does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Localizely API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Localizely API use?

Localizely uses an API token sent in the X-Api-Token header. The token must belong to a user with the Admin role in the project. Through Jentic, the token is stored encrypted in the vault and injected at execution time, so the raw value never enters agent context.

Can I work on translations in a feature branch instead of the main project?

Yes. POST /v1/projects/{project_id}/branches/{branch} creates a branch inside a project. Subsequent file upload and download calls scoped to that branch keep work-in-progress translations isolated until you merge them back.

What are the rate limits for the Localizely API?

Rate limits are not declared in the spec. Localizely applies plan-level limits at the account level; check your plan or contact support for the exact thresholds.

How do I check translation completion before shipping a release through Jentic?

Search Jentic for 'check translation completion status'. Jentic returns the GET /v1/projects/{project_id}/status operation. Load the schema, supply the project ID, and execute. The response is per-language completion that you can gate the deployment on.

Which file formats can I upload and download?

Localizely supports a range of localization file formats including JSON, YAML, .properties, .strings, and Android XML. The upload and download endpoints accept the file format you configured at the project level on the Localizely dashboard.