If a picklist field references reference data that has multilingual attributes in Reference 360, the business entity APIs can return the picklist field values in your preferred language. To return picklist field values in a language, use the optional Accept-Language request header .
For example, the Gender field of a business entity references a code list with a multilingual Name attribute that stores values in English (en-US) and Brazilian Portuguese (pt-BR). If you send a request with Accept-Language: pt-BR, the response returns Feminino as the Name value. If you send the request without the header, the response returns Female, the value in the default language.
The API matches the requested language tags against the languages in the Localization Languages code list in Reference 360. To return values in a language, add its BCP 47 language code to the Localization Languages code list. Then add values in that language for the multilingual attributes. Only the values of the multilingual attributes, such as Name, change based on the requested language. The Code value is the same in every language.
The following table describes the language of picklist field values that the API returns for each Accept-Language header value:
Accept-Language Header
Language of Picklist Field Values
Not specified or blank.
The default language defined in the Localization Languages code list.
Contains one or more languages in the Localization Languages code list, such as fr-FR or fr-FR,en;q=0.8.
The first language in order of preference that's in the Localization Languages code list. The API orders the language tags based on their quality values.
Contains a language that's specified in the Localization Languages code list, but the picklist field has no value or a blank value in that language.
The default language.
Contains only languages that aren't specified in the Localization Languages code list.
The default language. The API processes the request as if you didn't include the header.
For more information about multilingual reference data and the Localization Languages code list, see Manage multilingual assets in the Reference 360 help.
Effective in the October 2026 release, the ability to manage multilingual reference data is available for preview. Preview functionality is supported for evaluation purposes but is unwarranted and is not supported in production environments or any environment that you plan to push to production. Informatica intends to include the preview functionality in an upcoming release for production use, but might choose not to in accordance with changing market or technical circumstances. For more information, contact Informatica Global Customer Support.