Skip to main content
The Entri REST API gives you complete programmatic control over your localization workflow. Every action you can take in the Entri web application — creating projects, managing translation keys, triggering AI translation, importing and exporting files — is also available through the API.

​
Base URL

All API requests use the following base URL: 
https://api.nt3.io
If you are running a self-hosted instance, replace this with your own domain. Every endpoint is prefixed with /api/. For example, the endpoint to list your projects is: 
GET https://api.nt3.io/api/projects

​
API Version

The current API version is v1. Versioned endpoints are available at /api/v1/..., though the unversioned paths resolve to the same handlers. Breaking changes will be introduced under a new version prefix and announced in advance.

​
Interactive Documentation

A Swagger UI is available at /api/docs on any running Entri instance. It lists every endpoint with full request and response schemas, and lets you make test requests directly from the browser. 
https://api.nt3.io/api/docs

​
Quick Start

1

Create an API token

Go to your organization settings in the Entri web app and create an API token. The token will be displayed once — copy it and store it securely. All tokens are prefixed with entri_.
2

Make your first request

Pass the token in the X-API-Key header on every request:
curl https://api.nt3.io/api/projects \
  -H "X-API-Key: entri_your_token_here"
3

Explore the resources

Browse the endpoint reference in this section to learn what each resource supports.

​
Available Resources

Projects

Create and manage localization projects and their target languages.

Translation Keys

Create, update, and delete the keys that hold your translatable strings.

Translations

Read and write translation values, change status, and view history.

AI Translation

Trigger single or batch AI translation jobs for any key and language.

Import & Export

Upload existing translation files and download finished translations.

Glossary

Manage organization-wide terminology used by the AI and human translators.

Translation Memory

Browse and manage the organization-wide translation memory store.

Webhooks

Subscribe to real-time events such as translation completed or import finished.

API Tokens

Programmatically create, list, and revoke API tokens.

Activity

Retrieve the full audit trail for a project or organization.

Analytics

Fetch translation coverage and completion statistics.

Organization Settings

Read and update organization-level configuration.

​
Request Format

The API accepts JSON request bodies. Set the Content-Type header on any request that includes a body: 
Content-Type: application/json

​
Response Format

All successful responses return JSON. Collections return a data array alongside pagination metadata. Error responses follow a standard structure — see the Errors page for details.

​
Authentication

Two authentication methods are supported:
  • API Token — recommended for all programmatic access. Pass the token in the X-API-Key header.
  • Session Cookie — used by the web app. Not recommended for API clients.
See the Authentication page for full details and code examples.