Create localized content
Creates localized journey message content by cloning the message’s default content.
locale is required. Fields you provide will override the cloned default. The content field must be exactly one of mjml (email), html (email), text (email and SMS), or payload (push).
Unlike broadcasts, a journey does not need to be a draft to create localized content. A live or paused journey is editable. Archived and locked journeys are rejected with 409 Conflict, as are duplicate locales.
Authorizations
Accepts either a raw API key or Bearer <key>.
Headers
Optional dated API revision for the request. Must use YYYY-MM-DD format.
^\d{4}-\d{2}-\d{2}$"2026-03-01"
Body
Locale for the new content. Required, and must not already exist on this message.
255Subject line. Omit to inherit the default content's.
Preheader text. Omit to inherit the default content's.
Channel content body — exactly one of mjml, html, text, or payload.

