Skip to content

Transactional email

Receipts and resets, on the same server.

Send one-to-one email from your app through an HTTP API, with templates, a message log and webhooks. Marketing and transactional stay separate.

An API request that sends a password reset email, and the message log showing it delivered.

What you get

Transactional email, in detail.

  • An HTTP API

    POST a message with from, up to 50 recipients, a subject, HTML or text or a template with variables, tags and metadata. You get a message id per recipient.

  • Keys that only send

    Create API keys scoped to transactional email, so a leaked key can never read or change your audience.

  • Templates with variables

    Design a template once in the builder or in HTML, and call it by slug.

  • A log you can search

    Volume, delivery, bounce and open rates, and a message log with an event timeline for each message.

  • Webhooks for events

    Delivered, bounced and more, posted to your endpoint and signed.

  • Its own allowance

    Transactional volume has its own plan limit and never eats your marketing quota.

Also included

The small things that decide whether you use it.

  • API keys scoped to transactional
  • Tags and metadata on messages
  • Open and click tracking you can switch off
  • Status and events per message via the API

Questions

Good to know.

Can I send transactional email without marketing consent?
Yes. Transactional messages skip the marketing unsubscribe list, but never go to addresses that hard-bounced or complained.

Bring your list over this week.

Start on the Free plan in a minute, import your Mailchimp account, and send your first campaign from your own domain.