Features

Projects, Locales, Keys, and Values

Projects are where your translation work lives. A project usually maps to a product, app, website, package, or content area.

Use child projects when one product needs multiple independent translation sets under the same project family. For example, Tiko can have one parent project and API key access while keeping separate child projects for Talks, Cards, website copy, or other grouped content.

Concepts

Concept Meaning
Project A translation workspace.
Parent project A top-level translation workspace that owns shared language settings.
Child project An independent translation set nested below a parent project.
Source locale The language you write content in first.
Target locale A language you want Lezu to translate into.
Key A stable name for a piece of text, such as home.title.
Value The translated text for one key in one locale.

Create a Project

POST /v1/i18n/projects
Authorization: ApiKey lez_...
Content-Type: application/json

{
  "name": "Marketing Website",
  "sourceLocale": "en"
}

Response:

{
  "data": {
    "project": {
      "id": "project_123",
      "name": "Marketing Website",
      "sourceLocale": "en",
      "parentProjectId": null
    }
  },
  "meta": {}
}

Child Projects

Child projects let you keep multiple translation sets below one parent project without creating a separate language setup for each set.

A child project is still a normal project for imports, values, releases, bundles, and runtime usage. The difference is that it has a parentProjectId and inherits the parent’s setup when it is created.

Inherited from the parent:

  • Source locale.
  • Existing target locales.
  • New locales added to the parent later.
  • Auto-translate setting.
  • Translation tone preset and custom instructions.
  • Project color and icon unless overridden.
  • Same owner/API-key access model.

Not shared with the parent:

  • Translation keys.
  • Translation values.
  • Imports.
  • Releases and bundles.
  • Environments.

Use this when a product family needs one language policy but multiple content sets. For example, one Tiko parent project can have child projects for Tiko Talks, Cards, website copy, and admin copy.

Create Child Projects in the Dashboard

You can create child projects in two places:

  1. From Add Project:
    • Open the project switcher.
    • Choose Add Project.
    • Select a parent project in the Parent Project field.
    • Enter the child project name and create it.
    • Language and auto-translate controls are inherited and hidden for child creation.
  2. From Project Settings:
    • Open the parent project.
    • Go to Settings.
    • Use the Child Projects card to create a child project.
    • Existing child projects are listed there and can be opened directly.

Create a Child Project with the API

POST /v1/i18n/projects/project_123/children
Authorization: ApiKey lez_...
Content-Type: application/json

{
  "name": "Tiko Talks"
}

Optional overrides:

{
  "name": "Tiko Talks",
  "color": "blue",
  "icon": "message-circle"
}

Response:

{
  "data": {
    "project": {
      "id": "project_child_123",
      "name": "Tiko Talks",
      "sourceLocale": "en",
      "parentProjectId": "project_123"
    }
  },
  "meta": {}
}

List Child Projects

GET /v1/i18n/projects/project_123/children
Authorization: ApiKey lez_...

Response:

{
  "data": {
    "projects": [
      {
        "id": "project_child_123",
        "name": "Tiko Talks",
        "sourceLocale": "en",
        "parentProjectId": "project_123"
      }
    ]
  },
  "meta": {}
}

Import Into a Child Project

Use the returned child project id with the normal import endpoint:

POST /v1/i18n/projects/project_child_123/import
Authorization: ApiKey lez_...
Content-Type: application/json

{
  "locale": "en",
  "translateMissing": true,
  "content": {
    "cards": {
      "title": "Cards"
    }
  }
}

This keeps the child’s keys and values isolated from the parent while using the inherited language setup.

Read Values

GET /v1/i18n/projects/project_123/values
Authorization: ApiKey lez_...

Use values to show what has been imported, translated, reviewed, or prepared for release.

Relevant Endpoints

Method Endpoint Scope
GET /v1/i18n/projects i18n:read
POST /v1/i18n/projects i18n:write
GET /v1/i18n/projects/:projectId/children i18n:read
POST /v1/i18n/projects/:projectId/children i18n:write
GET /v1/i18n/projects/:projectId/values i18n:read
Features

More Pages