Templates
Update Template
Update an email template
PUT
Update Template
Update template metadata, labels, or content. You can pass an email template ID; transactional email IDs and slugs are also resolved for compatibility.
The double opt-in confirmation email is a regular email you edit here: get its ID from
consent.doubleOptInEmailId in tracking settings. New html or blocks for it must keep the {{DOUBLE_OPT_IN_URL}} link that confirms the subscription, otherwise the request returns 400 with Double opt-in confirmation emails must include {{DOUBLE_OPT_IN_URL}}. and nothing is saved. Name, subject and preview text changes are not affected.
Request
string
required
Template ID, transactional email ID, or transactional slug.
string
Updated template name.
string
Updated email subject line.
string | null
Updated inbox preview text. Send
null to clear it.string
Replacement HTML body. Use this or
blocks, not both.array
Replacement Sequenzy email blocks. Use this or
html, not both. Put block
styling under styles; top-level style keys like backgroundColor,
backgroundOpacity, textColor, textAlign, borderColor, borderWidth,
and borderRadius are normalized into styles.array
Replacement label names. Send an empty array to clear labels. Missing labels
are created automatically. The API also accepts
label as a compatibility
alias.boolean
Mark (
true) or unmark (false) this email as a reusable master design that
sequence steps and campaigns can start from.Responses
Content on an A/B test variant cannot be changed here. The 400 names
update_ab_test_variant so test status and live-change confirmation stay
enforced. When the key also has ab_tests:read, the error includes
abTests[] with every matching test and variant; otherwise those protected
identifiers are omitted. Get Template reports
the same collection on template.abTests before you write.