Localizejs Localize API

Name: Localize API
Brand: Localize API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationapiKey14 EndpointsREST

For Agents

Manage translation projects, phrases, glossary terms, and languages, and run bulk import and export operations against the Localize translation platform.

Install Jentic One Beta

Connect the Localize API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Localize API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Localize API.

Manage translation projects and the languages enabled on each

Create, update, and remove individual phrases attached to a project

Update a phrase translation for a specific language code in one call

GET STARTED

Start building with Localize API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Localize API, keeping it validated and agent-ready. Localize translates websites and applications without code changes, and the API exposes the underlying translation database to development and content teams. The endpoints cover projects, phrases, languages, and glossary terms, with bulk import and export operations for moving translation memory between environments. It is built around a project model where each project has its own phrases, languages, and glossary.

Use Cases

Patterns agents use Localize API for, with concrete tasks.

★ Continuous Translation Sync

Product teams shipping copy changes daily need translation memory to stay in sync across environments. Localize's bulk import endpoint accepts new and updated phrases, and the export endpoint pulls the current state for staging or QA. A scheduled job can move phrases between dev, staging, and production projects.

Call POST /v1/projects/{projectId}/import with the latest phrase set from the dev project, then GET /v1/projects/{projectId}/export from staging to verify.

Glossary-Driven Translation Quality

Companies enforcing brand voice across languages maintain a glossary of terms. The Localize API exposes the glossary per project so a translation review tool can flag any phrase that conflicts with a glossary term and suggest the approved translation. Glossary terms can be created and updated through the API as the brand voice evolves.

Pull GET /v1/projects/{projectId}/glossary and POST new terms when the marketing team adds approved translations for brand vocabulary.

AI Agent Translation Assistant

An AI agent helping a product manager localise a new feature can use Jentic to add phrases to the relevant Localize project, set translations for each enabled language, and confirm the import was clean. The agent never holds the API key; Jentic injects it at execution time.

Use Jentic to call POST /v1/projects/{projectId}/phrases for each new string the user provides and PUT translations for each enabled language.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/v1/projects

List translation projects

POST

/v1/projects/{projectId}/phrases

Add a phrase to a project

PUT

/v1/projects/{projectId}/phrases/{phraseId}/translations/{languageCode}

Set a translation for a phrase in a given language

POST

/v1/projects/{projectId}/import

Bulk import phrases

GET

/v1/projects/{projectId}/export

Bulk export phrases

POST

/v1/projects/{projectId}/glossary

Create a glossary term

GET

/v1/projects

List translation projects

POST

/v1/projects/{projectId}/phrases

Add a phrase to a project

PUT

/v1/projects/{projectId}/phrases/{phraseId}/translations/{languageCode}

Set a translation for a phrase in a given language

POST

/v1/projects/{projectId}/import

Bulk import phrases

GET

/v1/projects/{projectId}/export

Bulk export phrases

Why Jentic?

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

Credential isolation

Localize API keys are stored encrypted in the Jentic vault. The Authorization header is injected at execution time, so the raw key never enters agent context, logs, or LLM traces.

Intent-based discovery

Agents search Jentic for intents like 'add a phrase for translation' and Jentic returns the matching Localize operation with its input schema, so the agent can act on translation requests without browsing localizejs.com docs.

Time to first call

Direct Localize integration: 1-2 days for auth, project setup, and phrase + translation CRUD wiring. Through Jentic: under 1 hour to search, load schema, and execute.

FAQs

Specific to using Localize API through Jentic.

Why is there no official OpenAPI spec for Localize API?

Localize does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Localize 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 Localize API use?

Localize uses an API key sent in the Authorization header. Through Jentic, the key is held encrypted in the vault and injected at execution time, so the raw value never reaches the agent or its logs.

Can I add a phrase and translate it in one call?

Not in one call, but in two: POST /v1/projects/{projectId}/phrases creates the phrase, then PUT /v1/projects/{projectId}/phrases/{phraseId}/translations/{languageCode} sets the translation per language. Loop the PUT for each enabled language.

What are the rate limits for the Localize API?

Rate limits are not declared in the spec. Localize applies plan-level limits to API throughput; teams running heavy bulk imports should batch requests and respect any 429 backoff signals returned by the API.

How do I import a batch of phrases through Jentic?

Search Jentic for 'import translation phrases'. Jentic returns the POST /v1/projects/{projectId}/import operation. Load the schema, supply the project ID and the phrase payload, and execute. Use the matching export endpoint to verify.

Can I maintain a brand glossary alongside my translations?

Yes. The /v1/projects/{projectId}/glossary endpoints let you create and read glossary terms scoped to a single project. Pair them with the phrases endpoints to enforce consistent translation of brand vocabulary.

Localizejs Localize API

Connect the Localize API to your agent

Capabilities

Start building with Localize API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs