Connect Strapi
Import content from your self-hosted Strapi 5 into transglot and write reviewed translations into each document's target-locale localization.
| Direction | Two-way |
| Imported | The source-locale localization of the fields you map, on the content types you choose |
| Written back | Each document's target-locale localization. The source locale is never written |
| Sync | Sync from CMS |
| Per sync | Up to 1,250 documents per content type |
| Plan | Starter and above |
Before you start
- The connector targets Strapi 5 (documents addressed by
documentId). - Enable the Internationalization (i18n) plugin, add your target locales, and mark the fields you want translated as localized. Strapi's locale codes must match the language codes in your transglot project.
- Your Strapi must be reachable over https at a public address.
- Create an API token with read and write access (or a custom token scoped to your content types) in Strapi's API token settings.
Connect
Open your project's settings, choose CMS, and pick Strapi in the CMS list.
| Field | What to enter |
|---|---|
| Strapi base URL | Your Strapi instance root, for example https://cms.example.com. transglot adds /api/… itself |
| API token | The token you created |
| Content types | Plural API IDs of your collection types, comma separated, for example articles, pages |
| Translatable fields | Attribute names, comma separated |
| Publish these locales | The target locales to write back |
Select Connect, then Test connection. The test reads one entry of the first content type in your source locale.
What gets imported
transglot lists each content type in your project's source locale and imports the mapped attributes that hold text. When a document has a title attribute, its value becomes the description on the document's keys.
How translations are written back
Each locale is a separate localization of the same document. transglot writes each target locale with a request addressed to that locale, which creates the localization if it does not exist yet and updates it if it does. Other locales, including the source, are left as they were.
Troubleshooting
... the credentials were rejected.The token is wrong, expired, or lacks write access to the content type.... the endpoint or document was not found, check the base URL and content type.Check Strapi base URL and that each content type is the plural API ID.The webhook URL must use https.orThe webhook URL resolves to a private or reserved address.transglot only connects to a public https address.