Transloco Translator

About

Transloco Translator helps analysts, QA, and localization teams capture translation keys directly from a live web page and send them to a backend API you configure.
No more copying strings from the UI into spreadsheets or internal tools. Select visible text on your site, fill in translations per locale, and save — the extension uses a fixed, documented API contract (Transloco Protocol v1) so your backend team can implement once and support every project.
HOW IT WORKS
1. Add a connection: API base URL, site domains (where the tool should appear), and locales (e.g. uz, ru, en).
2. Set custom headers for authentication (Bearer token, Basic auth, or any header your API expects).
3. On an allowed page, select text — that text becomes the translation key.
4. Enter values for each locale and click Save. The extension calls your API (GET to prefill, PUT to create or update).
KEY FEATURES
• Text selection overlay on pages you allow (per-connection site patterns)
• Translation form with all configured locales
• Transloco Protocol v1 — standard GET/PUT /api/transloco/v1/entries/{key}
• Optional discovery endpoint (/.well-known/transloco.json) to sync locales
• Connection manager: add, edit, delete, import/export JSON
• Custom HTTP headers for auth (stored locally on the device)
• Downloadable protocol package for backend developers (OpenAPI, JSON Schema, guides)
• Test connection from the UI before going live
WHO IT IS FOR
Teams that use transloco / i18n and want a fast way for non-developers to add or update keys against their own translation API — staging, admin panels, or internal frontends.
PRIVACY & DATA
The extension does not send data to Transloco servers. Translations go only to the API URL you configure. Connection settings sync via Chrome storage; secrets (e.g. Authorization) stay in local storage on your device.
BACKEND REQUIRED
Your team implements Transloco Protocol v1 on your server (or uses the sample .NET + SQLite backend from the project). The extension includes a full spec download for implementers.
Support: configure site permissions when prompted so the extension can run on your app domains and reach your API.