Translations for Customer Form Fields (Beta)
The Translations Admin GraphQL API is currently available on Catalyst storefronts only.
The following entities are translatable for customer form fields:
- Label as
label- The display label for the form field - Option values as
option_{base64string}- Option values where the base64 string encodes the original option text
Resource fields
The entities listed above are referenced differently based on resource type and must use the following values in the queries outlined below:
Field Name Format for Options
label- The display label for the form fieldoption_{base64string}- Option values where the base64 string encodes the original option text- Example:
option_SG9tZSBBZGRyZXNz(whereSG9tZSBBZGRyZXNzis base64 for “Home Address”) - Example:
option_TW9iaWxl(whereTW9iaWxlis base64 for “Mobile”)
- Example:
Examples
Below are examples of GraphQL queries and mutations for retrieving and managing translation settings for customer form fields.
Query a List of Translations
This query returns a paginated list of translations by resourceType, channel, and locale with a maximum of 50 results per request.
The request below uses several variables for reusability. Replace {{channel_id}} and {{locale_code}} with the appropriate values for your use case.
Request
Response
Query a Translation by Resource ID
This query returns translation(s) by resourceId.
The request below uses several variables for reusability. Replace {{resourceId}}, {{channel_id}}, and {{locale_code}} with appropriate values for your use case. Make sure resourceId follows the format from the Resource fields table.
Request
Response
Update a Translation
This mutation updates a translation.
Request
Response
The mutation example above shows a successful response. If an entity is not found, the API will return an error response. See the Error Handling Reference for more details on error responses.
Example error response for entity not found:
Delete a Translation
The following mutation deletes a translation.