DevTools

Translate files, call the API from your server, and render multilingual applications with JavaScript packages.

Localization connects two kinds of code: the code that produces translations and the code that uses them. A server may request translated content when a record changes. A build may collect translated files. A React component may read an existing catalog without making a translation request at all.

Start with the part you are implementing. Each section has a complete first task followed by the contracts needed for ongoing work.

API #

Use the API when your server already holds the content and should decide when to request a translation, where to store it, and when to use it. Submit JSON content or uploaded files as a translation job, start it, and retrieve each completed target. The engine controls its translation and review stages.

Make your first request sends a small payload and saves the translated data locally. The recipe explains the credential, localization engine selection, response fields, and checks before you connect it to application storage.

CLI #

Use the CLI when content lives in files. Configure the source paths and target locales, submit the selected work, and retrieve target files into your project. The CLI records source baselines so later runs can process changes instead of treating every file as new.

Translate your first file covers installation, authentication, configuration, and retrieval. The same CLI can extract explicit React messages into catalogs; extraction is local and does not request translations.

JavaScript #

The JavaScript packages cover server clients, React message rendering, and locale routing. Choose a client for translation requests or a rendering library for messages already available to the application. Browser rendering does not need a translation API key.

The React documentation includes a local first-message example, catalog loading, grammatical alternatives, rich text, and framework-specific integration. URL negotiation and translated text are separate responsibilities, so the routing references explain how to keep the selected locale and loaded messages together.

Bring an existing project #

Formats explains what each handler translates and reconstructs. Check the invoking tool's format list too: a handler available to a server integration is not necessarily a configured CLI file format.

Projects using i18n.json or LingoDotDevEngine have versioned CLI v0 and SDK v0 references. Keep the installed version while planning migration; configuration, retained state, and return values can change between generations.

For an assistant working on local files or account configuration, use MCP. For translation connected to a repository, CMS, or help center, use Integrations. Each connection defines how work starts, what authority it uses, and where results return.