create_key
Create translation keys in Texterify to identify i18n strings in your codebase. Configure HTML formatting and pluralization, then populate translations separately.
Instructions
Create a new translation key (i18n string identifier) in the configured Texterify project. This only creates the key entry — it does NOT add any translated content. After creating a key, call set_translation for each language to add translations. Key names must be unique within the project; duplicate names return a validation error with code "TAKEN". Typical workflow: create_key -> list_languages -> set_translation for each language.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | The Texterify project UUID. You can find this value in the project's texterify.json file under the 'project_id' field | |
| name | Yes | The key name used as the i18n identifier in source code, typically in snake_case or dot.notation (e.g., 'welcome_message', 'auth.login.title'). Must be unique within the project | |
| description | No | Optional human-readable description to help translators understand the context (e.g., 'Greeting shown on the homepage header'). This is not the translation — it's metadata about where/how the key is used | |
| html_enabled | No | Set to true if translation values for this key contain HTML markup. When enabled, the Texterify UI shows a rich text editor for translators. Defaults to false | |
| pluralization_enabled | No | Set to true if this key needs plural forms (e.g., '1 item' vs '5 items'). Follows CLDR Plural Rules with forms: zero, one, two, few, many, and other (the content field). When enabled, use the plural parameters in set_translation. Defaults to false |