Internationalization API
REST API for Internationalization and Localization.
Strings are localized by specifying translations for each necessary language. In each
API, you can specify a language using the "Accept-language" header.
This header can contain a comma-separated list of languages, for example,
ru-RU,ru;q=0.8,en-US;q=0.6,en;q=0.4 or en-US;q=0.6,en;q=0.4- for
details see https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
Important: To support locales based on specific language variants (e.g.
en-GB), not just languages (e.g. en),
Internationalization API is using xx-YY in all cases, and i18n API
users should always specify xx-YY in i18n request headers. For each localizable element returned by Reltio, the system tries to use a translation for the first language specified. Then (if not found) for the next language, and so on. If no translations are found, the value from Business Model will be used as is.
Note: The
POST {TenantURL}/resources/i18n internationalization API supports localization of label patterns, direction labels, error messages, and, customer-defined lookups. The labels, abbreviations, captions, and descriptions can be localized by modifying the UI configuration.| Localization Scope | Localization Support |
|---|---|
| Desktop UI | UI Configuration |
| UI Configurations | UI Configuration |
| Metadata: labels | UI Configuration |
| Metadata: data label patterns | Internationalization API |
| Lookups | Internationalization API |
| Errors | Internationalization API |
Note: To localize items that are not supported by Internationalization API, you should
contact Reltio Professional Services or Reltio Customer Support with a Localization
Request. For more information see Setting Up Localization.