Build ICU skeletons
Generates ICU (International Components for Unicode) message format skeletons for a given source string across one or more locales. An ICU skeleton strips the literal text from a pluralized or select message while preserving its structural rules — argument names, plural categories, select cases, and ordinal forms — adjusted to the pluralization rules of each requested locale.
Use this endpoint to normalize translation templates before importing them into locale files, or to validate that a source string carries the plural forms required by a target language.
Either content or id must be provided — supplying both or neither returns 400. When id is used and the referenced translation does not exist, the endpoint returns 404. When the source string is not valid ICU message format syntax, the endpoint returns 422 with an error field describing the parse failure.
Authorizations
Enter your token in the format token TOKEN
Headers
Two-Factor-Authentication token (optional)
Body
- icu/skeleton/parameters
- icu/skeleton/parameters
Source ICU message string to derive skeletons from. Mutually exclusive with id; exactly one of the two must be provided.
"{count, plural, one {One item} other {# items}}"
Code of an existing translation to source content from. Mutually exclusive with content; exactly one of the two must be provided. Returns 404 when the translation does not exist.
"abcd1234abcd1234abcd1234abcd1234"
Locale codes for which to generate skeletons. The pluralization rules of each locale determine which plural forms appear in the output.
When true, preserves the existing translation text in each plural form and adds any missing forms for the locale rather than stripping all literal content.
false
When true, includes the zero plural form in the generated skeleton for locales that support it.
false
Pluralization rule set to use when constructing skeletons. Pass legacy for pre-CLDR behaviour, or a CLDR version string such as cldr48. Defaults to the project's configured version when omitted.
"cldr48"
Response
OK
Object keys are dynamic and based on requested locale codes, see example.