A project is the top-level container for your localization work. Each project has a source language (the language your strings are written in) and one or more target languages that you want to translate into. All translation keys, translations, AI jobs, imports, and exports live under a project.
Projects are scoped to an organization. API tokens are associated with an organization, so all project endpoints automatically filter to the organization that owns the token.
Endpoints
Create a Project
Response:
List Projects
Returns all projects belonging to your organization.
Get a Project
Update a Project
All fields are optional — only the fields you include will be updated.
Archive a Project
Deleting a project archives it rather than permanently destroying it. Archived projects and their data are retained for a recovery period.
Permanently Delete a Project
Permanently deletes a project and all of its data: translation keys, translations, key and translation history, comments, project-scoped translation memory entries, project-scoped webhooks, and project-scoped API tokens. Activity logs are retained at the organization level as an audit trail, including a final project.deleted entry.
Unlike the other project endpoints, this endpoint cannot be called with an API key. It requires the session cookie of a signed-in organization owner:
Response:
This action cannot be undone. Requests from any non-owner role — or authenticated with an API key, which carries no member session — receive a 403 Forbidden.
Manage Target Languages
Add a language to a project’s target language list:
Remove a target language:
Removing a target language does not delete the existing translations for that language, but the language will no longer appear in the editor or be returned by export endpoints.
Key Notes
- Language codes follow the BCP 47 standard (for example
en, fr, zh-TW, pt-BR).
- The
sourceLanguage of a project cannot be changed after creation.
- Every action on a project is recorded in the Activity log.