- Add translations or update existing ones as needed.
- Retrieve a list of all translatable fields, and their translations if available.
Before you begin
Review the following before you begin:- There are 2 types of content you can translate:
staticTranslations: Fixed interface elements such as button labels and headers.dynamicTranslations: Content-specific values you define, such as product prefixes.
- The original content is in English,
en, which serves as the default language when no translation is provided for a field. - You can only add translation content for locales that already have a language set up.
- If you’re using the Game Portal, you can only use this API to translate Game Portal pages, including the web store page. To translate Game Portal content, see Translate Game Portal Content.
Workflow for using the Translations API service
This API service is intended to be used in a specific sequence as part of a defined flow:- Add a new language in the Publisher Dashboard. Each time a new langugage is added, a new object is added to the API for each field.
- Call the Get Translations API to get a list of all translatable fields, including both
staticTranslationsanddynamicTranslationsstrings. - Translate the content for the available languages.
- Call the Set Translations API with the translated fields.
- Activate the language in the Publisher Dashboard:
- Go to the Localization tab.
- Scroll to Manage Languages.
- Turn on the toggle for each language you want to make available to customers.
To keep translations current, repeat steps 2- 4 regularly.
