Skip to main content

Send transactional email from a template

Transactional templates let you build a message once — layout, branding, and personalization tokens — then send it programmatically with per-recipient data merged in at send time. This keeps receipts, password resets, order confirmations, and similar one-to-one messages consistent while your application supplies only the values that change.

Before you begin​

  • An API key or credential with permission to send transactional email (confirm the exact steps in your account).
  • A reusable template that an Author has published for transactional use, with personalization tokens in place for every dynamic value.
  • The template's identifier (an ID or name) so your request can reference it.
  • A test subscriber address you can safely send to while validating.

Steps​

  1. In the app, open the transactional template and note its identifier. Confirm that each dynamic value (name, order number, reset link) uses a personalization token rather than hard-coded text.
  2. In your application, build the send request: reference the template by its identifier, set the recipient's email, and provide a set of key-value pairs whose keys match the template's tokens exactly.
  3. Include any per-send options your account supports, such as reply-to or a tracking flag (confirm the exact fields in your account).
  4. Send the request to the transactional endpoint and capture the response, including the message identifier, for logging and later lookups.
  5. Handle errors: a missing token value, an unknown template ID, or a suppressed address will be rejected — surface these so your application can retry or alert.

Result​

The subscriber receives the rendered message with their data merged in, and your application logs a message identifier it can use to check delivery status. Send to your test address first and confirm every token resolved before going live.

Canonical terms: Author, Edition, Folder (Project Folder), Broadcast. See the Glossary.