Skip to main content
POST
/
icu
/
skeleton
cURL
curl "https://api.phrase.com/v2/icu/skeleton" \
  -u USERNAME_OR_ACCESS_TOKEN \
  -X POST \
  -d '{"content":"{number, plural, one {One} other {%{n}}}","locale_codes":["en"],"zero_form_enabled": true}' \
  -H 'Content-Type: application/json'
{
  "en": "{number, plural, one {} other {}}",
  "de": "{number, plural, one {} other {}}"
}

Authorizations

​
Authorization
string
header
required

Enter your token in the format token TOKEN

Headers

​
X-PhraseApp-OTP
string

Two-Factor-Authentication token (optional)

Body

application/json
​
content
string

Source content to derive skeletons from. Mutually exclusive with id; exactly one of the two must be provided.

Example:

"{number, plural, one {One} other {%{n}}}"

​
id
string

Translation code to source content from. Mutually exclusive with content; exactly one of the two must be provided.

Example:

"abcd1234abcd1234abcd1234abcd1234"

​
locale_codes
string[]

Locale codes

Example:
["en"]
​
keep_content
boolean

Keep the content and add missing plural forms for each locale

Example:

null

​
zero_form_enabled
boolean

Indicates whether the zero form should be included or excluded in the returned skeletons

Example:

null

​
cldr_version
string

Strings supports two CLDR variants, when it comes to pluralization rules.
You can choose which one you want to use when constructing the skeletons. Possible values
are legacy and cldr_41. Default value is legacy.

Example:

"cldr_41"

Response

OK

​
locale_code
string

Object keys are dynamic and based on requested locale codes, see example.