Update email template
Update an email template: rename, change the subject or senders, replace its content, or publish/unpublish it (status). Content is re-rendered server-side. Sending html to a block template converts it to an HTML template, one way — an HTML template cannot take a document again. A PUBLISHED template is live: journeys that send it use the change from their next send, so any update to one requires confirm: true (call without it first to see the refusal). Omitted fields are unchanged.
Authorizations
Organization API key, sent as Authorization: Bearer boom_org_....
Path Parameters
Email template id.
1Body
11Block-builder content. Send exactly one of document or html.
Hand-written HTML (the template becomes an HTML template). Sanitized on save — scripts, event handlers and external stylesheets are removed and listed in removed. Variables use the same {{path}} grammar.
1Sender id to send From. Must be on the verified domain (usableAsFrom in journeys_email_templates). Null/omitted = the org default.
Sender id for Reply-To. Null/omitted = the org default.
PUBLISHED makes it usable by SEND_EMAIL nodes; DRAFT withdraws it, and journeys that send it will then fail to send.
DRAFT, PUBLISHED Must be true to change a template that is PUBLISHED.