Wakio
Transactional
Receipts and resets, on your own domain.
One API sends from a domain you have proved you control, with your own sending reputation and a suppression list that is yours alone.
How it works
From a new domain to a delivered receipt.
-
1
Add your domain
Publish the DNS records Wakio gives you. The domain can send once its DKIM records verify and a challenge shows your account controls it.
-
2
Send with one request
POST to /v1/emails with an Idempotency-Key header. A retry with the same key and body within 24 hours gets the first answer back and sends nothing new.
-
3
Read every event
Each recipient's delivery records when it was accepted, then every delivery, bounce and complaint with its time. A bounce keeps the reason the receiving server gave.
Per-account suppression
Someone else's bounce is never your problem.
Your suppression list belongs to your account alone, and every send checks it first. A hard bounce for another sender never quietly blocks that address for you.
Headroom
Receipts keep moving during a big send.
Transactional mail is picked up first, ahead of automation and campaigns, and marketing mail can only ever spend part of each day's sending budget. Receipts also keep sending after you pass your plan's allowance.
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.