A template is part of the sending contract. Approval, publication and event authorization each answer a different question in the workflow.
Choose a supported customer action
Start with a real account, security, order, payment or appointment event. Select the matching catalog template for the verified domain.
A draft or customer-published template can remain editable without becoming eligible for production sending. Keep marketing and broadcast content outside this transactional path.
Supply only allowed variables
Use the template’s documented variable names and types. The renderer bounds values and rejects unknown or reserved variables before admission.
Keep links on the verified domain where the contract requires them, and never place secrets or personal data in a public example or log.
Treat edits as a new version
When you publish an edited template, the next installation creates a fresh approved version while preserving the earlier record. Pin the version used by a queued message.
Changing a template does not authorize an event. The exact event, recipient and content remain bound at validation and immediately before SMTP.
Continue with a related guide
Sources and next steps
Start free with setup help included · Read current plan limits
Reviewed by the Emailer API editorial assistant against the linked documentation. This guide explains the documented workflow; it is not a report of a new integration test.