Skip to content
Wakio
Get started
Transactional Broadcast Automation Pricing Docs Sign in

Every email your business sends, from one place.

Receipts, password resets, newsletters and welcome series, all sent from your own domain with your own sending reputation. A suppression list that is yours alone, and every delivery event kept where you can read it.

Get started See pricing

Transactional mail keeps sending while a campaign is mid-flight and after you pass your allowance. You're warned at 80%.

A campaign mid-send in the Wakio dashboard: 270,418 recipients, 183,661 delivered and 84,398 still to send, with pause and cancel controls

Sends for

For your marketing

Newsletters from the same account

Write it in the composer, send it to a list, and watch it go out in paced waves. Pause, resume or cancel while it runs.

See broadcast
The Wakio campaign composer: an audience picker set to every active contact, a subject line, and a rich-text body with merge fields

For your developers

One endpoint for every receipt

One endpoint, idempotent by key. Each recipient gets its own delivery record, with the time it was accepted and every delivery, bounce and complaint after it. 

curl https://api.wakio.net/v1/emails \
  -H "Authorization: Bearer $WAKIO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-1042-receipt" \
  -d '{"to":"[email protected]","subject":"Your receipt","html":"<p>Order 1042 is paid.</p>"}'
See transactional Read the API docs
The Wakio deliveries log: receipts and password resets sent through the API, one row per recipient, marked delivered, bounced or queued
Why it lands

Deliverability is the product, for every kind of email.

Everything below protects your domain, whether the message is a receipt or a newsletter.

Per-account suppression

Someone else's bounce is never your problem

Your suppression list belongs to your account alone. A hard bounce for another sender never quietly blocks that address for you.

[email protected]suppressed · your account
[email protected]sendable · everyone else
Domain ownership

Two proofs before a message can leave

A domain sends once its DKIM records verify and a challenge shows this account controls it.

DKIMverified
ownership challenge2026-04-12 09:41
One API

Idempotent by key

Retry a send without sending twice. The key is yours, and a repeat gets the first answer back.

POST /v1/emails202
POST /v1/emails202 replayed
Event trail

Every event, kept and readable

Accepted, delivered, bounced, complained. Each is stored per recipient with its timestamp, and a bounce keeps the reason the receiving server gave.

queued[email protected]12:03:51.902
delivered[email protected]12:03:53.417
bounced[email protected] · hard · mailbox does not exist12:03:54.802

Leaving Mailchimp

Bring your Mailchimp list. Mail only the people who said yes.

Upload the CSVs Mailchimp exports. Each contact's consent is graded from what Mailchimp recorded, unsubscribed and cleaned addresses become suppressions, and the report stays on the import for later.

How the import works
A finished Mailchimp import report: 41,402 rows accepted and 2,468 rejected of 43,870, broken down by subscriber status, with 3,100 addresses suppressed

Automation

The emails that send themselves.

A welcome series that starts when someone joins a list, or an email on a date you store for each contact, sent inside the hours you choose.

See automation
A three-step welcome series in Wakio, triggered when someone joins a list, with sent and opened counts for each step

Start with the email you already send.

Connect a domain, send your first receipt through the API, and bring your list over when you're ready.

Get started