Transactional + marketing email

Email for your app and your list, from one place.

Send sign-in links and receipts through the API or SMTP, and newsletters and onboarding flows from the dashboard. Every message shares one contact list, one suppression list and one log.

Get started Switching from Brevo?

Delivered through Amazon SES. Every new sender is reviewed before they can send.

send.sh

# Send from your app
curl https://app.mailrail.io/api/v1/emails \
  -H "Authorization: Bearer mr_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-1234" \
  -d '{
    "from": {"email": "hello@yourapp.com"},
    "to": [{"email": "ada@example.com"}],
    "template": "receipt",
    "params": {"total": "$49.00"}
  }'

# → 202 {"id": "msg_...", "status": "queued", ...}

Everything a product team sends

The parts you would otherwise stitch together from a sending API, a newsletter tool and a forms service.

API and SMTP relay

A REST API with templates and idempotency keys, plus an SMTP relay on 587 and 465 for apps and auth libraries that only speak SMTP.

Campaigns

Send now, at a set time, at each contact's local time, or at the hour they usually open. Repeat daily, weekly or monthly, optionally from a JSON feed.

Automations

Welcome series, trial reminders and win-backs, triggered by a list join, an event from your app, or a date on the contact. Waits, branches and exits.

Lists, segments and forms

Contacts with attributes, rule-based segments, and hosted or embedded signup forms with double opt-in and a preferences page.

Editor with an AI designer

Build emails from blocks or raw HTML with your brand kit, versioned templates and shared blocks. Or describe the email and let the designer draft it.

Numbers you can trust

Apple Mail privacy opens and link scanners are counted apart from people, and purchases from your app are credited to the email that drove them.

Switching from Brevo is a config change

Mailrail accepts Brevo's request bodies and returns Brevo's response shapes for transactional email, contacts, list membership and events. Your existing calls keep working.

Add your sending domainPublish the DKIM and bounce records shown in the dashboard.
Bring your templatesBrevo template syntax renders as is. Give each template its old Brevo id so templateId still resolves.
Swap the base URL and keyPoint your client at Mailrail and send a Mailrail key in the same api-key header.

.env

BREVO_BASE_URL=https://api.brevo.com/v3
BREVO_BASE_URL=https://app.mailrail.io/api/v3

BREVO_API_KEY=xkeysib-...
BREVO_API_KEY=mr_...

# Same endpoints, same payloads:
#   POST /v3/smtp/email
#   POST|GET|PUT|DELETE /v3/contacts
#   POST /v3/contacts/lists/{id}/contacts/add
#   POST /v3/events

Your inbox placement doesn't depend on strangers

On shared sending, one careless sender can hurt everyone. Mailrail reviews every new workspace, starts it at a low daily limit, and stops anyone whose mail people don't want.

Review

Every new sender is approved by a person who checks the website, the domain and where the list came from. Bought or scraped lists are not allowed.

200/day

New senders start small. The limit steps up automatically, to 50,000 a day, while bounces stay under 2% and complaints under 0.05%.

Guard

Campaigns pause on their own when bounce or complaint rates climb, and only resume with a confirmation. Held mail is spread out again, never sent in a burst.

Suppress

Hard bounces, complaints and unsubscribes are never mailed again. One-click unsubscribe headers go on every campaign, as Gmail and Yahoo require.

Start sending with Mailrail

Create a workspace, add your domain, and apply to send. Most of the setup is copying DNS records.

Get started Sign in