Skip to main content
A translation key represents a single translatable string in your application. Each key has a unique identifier (the key name), an optional description that provides context for translators, and optional tags for organization. The actual translation values for each language are stored separately on the Translations resource. Keys are always scoped to a project. All key endpoints require a :projectId path parameter.

Endpoints

Create a Key

Response:

List Keys

Key listing is paginated. See Pagination for details.
Response:

Get a Key

Update a Key

All fields are optional — only included fields are changed.

Delete a Key

Deleting a key also removes all of its translations across all languages.

Bulk Operations

Use bulk endpoints when creating, updating, or deleting many keys at once. This is significantly more efficient than individual requests and reduces the risk of hitting rate limits. Bulk create:
Bulk delete:

Key Notes

  • Key names must be unique within a project. Attempting to create a duplicate key name returns 409 Conflict.
  • The Entri CLI uses bulk create internally when you run entri push.
  • Tags and namespaces are optional but help organize large key sets in the editor.