Features
I18n JSON Imports
JSON imports are the fastest way to bring existing app translations into Lezu.
How It Works
- Send nested JSON content to a project.
- Lezu turns nested paths into stable translation keys.
- The source-language values are added to the project.
- Optional target languages can be translated at the same time.
- You can publish releases after the content is ready.
Import Source Content
POST /v1/i18n/projects/project_123/import
Authorization: ApiKey lez_...
Content-Type: application/json
{
"locale": "en",
"content": {
"home": {
"title": "Welcome back",
"cta": "Start now"
},
"billing": {
"upgrade": "Upgrade plan"
}
}
}
Import and Translate
{
"locale": "en",
"targetLocales": ["nl", "fr", "de"],
"translateMissing": true,
"content": {
"home": {
"title": "Welcome back",
"cta": "Start now"
}
}
}
This imports English first, then creates missing translations for Dutch, French, and German.
Key Mapping
Nested JSON paths become dot-notation keys:
home.title
home.cta
billing.upgrade
Relevant Endpoints
| Method | Endpoint | Scope |
|---|---|---|
POST |
/v1/i18n/projects/:projectId/import |
i18n:write |
GET |
/v1/i18n/projects/:projectId/values |
i18n:read |
POST |
/v1/translate/estimate |
translate:read |