Transactional email

Receipts that look like your product.

Order confirmations, password resets, receipts. Built in the same editor as your campaigns, sent from your backend, and kept out of the marketing stream.

POST /api/v1/transactional_emails
{
  "key": "receipt",
  "email": "[email protected]",
  "data": {
    "amount": "$49.00",
    "plan": "Team"
  }
}
 
202 Accepted
receipt · rendered
Thanks, Dana
Your payment of $49.00 for the Team plan went through.
Sent from mail.yourcompany.com · no unsubscribe link
Send by key

One call from
your backend.

Give a template a key, then post to the API with an email address and a data object. Pombo renders and sends it. No SMTP wiring, no separate template store to keep in sync.

  • →POST /api/v1/transactional_emails with a key and recipient.
  • →Sends to anyone, contact or not. Addresses that bounced or complained are refused.
  • →The same send is available over MCP for an agent to test.
template keys
receipt              bound to no event
password-reset        bound to no event
welcome              event: user.created
shipping-update      event: order.shipped
Or trigger from an event

Bind a template
to an event name.

Post an event like order.shipped and the bound template fires automatically. Everything in the event payload is available as merge data in the template, per event, not per contact.

  • →A sequence and a transactional template can share one event and both run.
  • →{{ event.tracking_url }}, {{ event.amount }}, whatever you send.
  • →Settings, Events shows which templates each event fires.
EVENT
order.shipped
properties: tracking_url, carrier
FIRES
shipping-update template
rendered with {{ event.tracking_url }}
FROM
per-template from address
The difference from campaigns

No unsubscribe link,
by design.

Transactional mail is a one-off message a person needs, so it carries no unsubscribe footer and does not check marketing consent. It still runs on the same authenticated domain, with the same bounce handling and the same editor.

  • →Same block editor and layouts as campaigns and sequences.
  • →Same domain authentication: DKIM, SPF, DMARC, all passing.
  • →Hard bounces are still suppressed automatically.
campaign vs transactional
campaign       unsubscribe footer   consent checked
sequence       unsubscribe footer   consent checked
transactional  no footer            always delivered

Wire up your first
transactional email.

Build the template, give it a key, and post one request. The full platform is free to try.