Message template translations

A message template is one SMS or WhatsApp text: one message type and channel, addressed here by the id that List message templates and Get a message template return. Its content translates per store language; a customer whose language has a translation receives it, every other customer the template's own text. A translation keeps the original's values and tags exactly ({{ ... }} and {% ... %}, in any order within the same block): only the text around them changes, and one that does not is refused with MARKETING_TRANSLATION_VARIABLES_MISMATCH and details.variables listing what to keep. It must not be blank (MESSAGE_TEMPLATE_CONTENT_REQUIRED) and holds at most the template's max_content_length characters (MESSAGE_TEMPLATE_CONTENT_TOO_LONG). A translation written against an earlier original is reported outdated. Store Admin, the Tringify mobile app, translation CSV (resource message_template), AI translation and MCP translate the same texts. Each change sends message_templates/translations/update, or message_templates/translations/delete when a translation is cleared. Returns a resources entry keyed by message_template:{id} for each requested template (at most 100 per call); a template without a translation has an empty object. Fields without a translation in this locale are omitted from the response. An omitted field is not empty: shoppers see the store's base-language value, which the resource's own GET endpoint returns.

A message template is one SMS or WhatsApp text: one message type and channel, addressed here by the id that List message templates and Get a message template return. Its content translates per store language; a customer whose language has a translation receives it, every other customer the template's own text. A translation keeps the original's values and tags exactly ({{ ... }} and {% ... %}, in any order within the same block): only the text around them changes, and one that does not is refused with MARKETING_TRANSLATION_VARIABLES_MISMATCH and details.variables listing what to keep. It must not be blank (MESSAGE_TEMPLATE_CONTENT_REQUIRED) and holds at most the template's max_content_length characters (MESSAGE_TEMPLATE_CONTENT_TOO_LONG). A translation written against an earlier original is reported outdated. Store Admin, the Tringify mobile app, translation CSV (resource message_template), AI translation and MCP translate the same texts. Each change sends message_templates/translations/update, or message_templates/translations/delete when a translation is cleared. Each row is one template in one language: id, locale (any enabled non-default store locale) and fields. Rows for several languages can be mixed in one call; send at most 100 rows (one row = one template in one locale) and at most one row per template and locale. Each row is saved on its own: a failing row never stops the others. Empty values clear the matching field translation; omitted fields keep their translation. Every row is validated exactly like the single translation endpoint. The response has totals (rows, saved, failed) and one results entry per row in request order: {id, locale, status} with status saved or failed. A failed row carries the full error (code, message, details); its codes are the single endpoint's codes plus TRANSLATION_ROW_DUPLICATE. A saved rich-text row whose unsafe markup was removed lists warnings. A top-level code and message give the outcome: TRANSLATIONS_SAVED (200, every row saved), TRANSLATIONS_PARTIALLY_SAVED (200, success: true; the message counts saved and failed rows and names the failure reasons, e.g. "2 saved, 1 failed. No source text found for the requested fields (description).") TRANSLATIONS_NOT_SAVED_RETRY (503 with a Retry-After header, success: false; no row saved because every row failed only with TRANSLATION_WRITE_BUSY, so the same call can be sent again after error.details.retry_after_seconds) or TRANSLATIONS_NOT_SAVED (422, success: false; no row saved and at least one row failed for another reason). Both carry the same totals and results in error.details. With an Idempotency-Key, repeating the same request re-applies nothing that already saved and retries the failed rows. A write waits at most 2 seconds for other translation writes of the same item or of a clashing name or slug (for example a translation CSV import writing the same language); writes of other items, types and languages never wait. A row or call that fails with TRANSLATION_WRITE_BUSY (HTTP 503) saved nothing: send it again after error.details.retry_after_seconds (the call's Retry-After header says the same). Every row or call either saved or reports an error; none is left in an unknown state.

A message template is one SMS or WhatsApp text: one message type and channel, addressed here by the id that List message templates and Get a message template return. Its content translates per store language; a customer whose language has a translation receives it, every other customer the template's own text. A translation keeps the original's values and tags exactly ({{ ... }} and {% ... %}, in any order within the same block): only the text around them changes, and one that does not is refused with MARKETING_TRANSLATION_VARIABLES_MISMATCH and details.variables listing what to keep. It must not be blank (MESSAGE_TEMPLATE_CONTENT_REQUIRED) and holds at most the template's max_content_length characters (MESSAGE_TEMPLATE_CONTENT_TOO_LONG). A translation written against an earlier original is reported outdated. Store Admin, the Tringify mobile app, translation CSV (resource message_template), AI translation and MCP translate the same texts. Each change sends message_templates/translations/update, or message_templates/translations/delete when a translation is cleared. Returns the stored content translation in the selected locale with is_outdated; a template without a translation in this locale returns an empty fields object. Fields without a translation in this locale are omitted from the response. An omitted field is not empty: shoppers see the store's base-language value, which the resource's own GET endpoint returns.

A message template is one SMS or WhatsApp text: one message type and channel, addressed here by the id that List message templates and Get a message template return. Its content translates per store language; a customer whose language has a translation receives it, every other customer the template's own text. A translation keeps the original's values and tags exactly ({{ ... }} and {% ... %}, in any order within the same block): only the text around them changes, and one that does not is refused with MARKETING_TRANSLATION_VARIABLES_MISMATCH and details.variables listing what to keep. It must not be blank (MESSAGE_TEMPLATE_CONTENT_REQUIRED) and holds at most the template's max_content_length characters (MESSAGE_TEMPLATE_CONTENT_TOO_LONG). A translation written against an earlier original is reported outdated. Store Admin, the Tringify mobile app, translation CSV (resource message_template), AI translation and MCP translate the same texts. Each change sends message_templates/translations/update, or message_templates/translations/delete when a translation is cleared. Only content is translatable. Send an empty string to clear the translation; customers in that language then receive the template's own text. A write waits at most 2 seconds for other translation writes of the same item or of a clashing name or slug (for example a translation CSV import writing the same language); writes of other items, types and languages never wait. A row or call that fails with TRANSLATION_WRITE_BUSY (HTTP 503) saved nothing: send it again after error.details.retry_after_seconds (the call's Retry-After header says the same). Every row or call either saved or reports an error; none is left in an unknown state.