The EmailerThe Mail Your Users
Are Waiting For, Delivered.
The Emailer is the calm, dependable pipe behind your verification codes, receipts, alerts, and digests. No missing codes. No chasing bounces. Just mail that arrives.
curl https://api.theemailer.com/v1/messages \
-H "Authorization: Bearer $TE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "ada@customer.io",
"template": "verify-code",
"data": { "code": "418205" }
}'
# → 202 Accepted { "id": "msg_01HZKQ6R8P", "status": "queued" }From API Key To First Send In A Coffee Break.
Add Your Domain
Point a few DNS records at The Emailer. We handle SPF, DKIM, and DMARC alignment so mail signs cleanly from day one.
Drop In The API
One endpoint, one API key. A few lines of code sends a verification code, a receipt, or a password reset from any stack.
Watch Every Send
Real-time logs show delivery, opens, bounces, and complaints. Search by recipient, template, or message id.
Everything You Need. Nothing You Don't.
Verification And Reset
Codes and magic links that reach the inbox in seconds, not minutes.
Receipts And Invoices
Clean, itemized transactional mail that your customers can find later.
Account And Security Alerts
The mail your users notice: new device sign-ins, plan changes, refunds.
Daily And Weekly Digests
Batch summaries of the activity people opted in to hear about.
Real-Time Delivery Logs
Every attempt, every response, searchable and exportable.
Automatic Suppression
Hard bounces and complaints go on the list. A bad address is never mailed twice.
We Protect Your Sender Reputation Like It's Ours.
Every new sender is reviewed before their first send, and outgoing mail is screened to block anything that isn't one-to-one transactional. Every message is signed, aligned, and rate-shaped for the receiving domain. Hard bounces and complaints go straight to your suppression list, so a bad address never gets a second try. That discipline is why your codes land in the inbox.
- New senders reviewed before their first send
- Outgoing mail screened to block non-transactional content
- SPF, DKIM, and DMARC configured for you
- Automatic bounce and complaint suppression
- No spam, no purchased lists, no exceptions
Every Send, Down To The Handoff.
Search by recipient, template, or message id. See the SMTP response verbatim, the retry ladder, and the exact moment the receiving server said yes. When a customer says "I never got the code," you can prove what happened in seconds.
- Live stream of every attempt
- Full response body, not a summary
- Suppression status inline on the row
- Exportable to CSV or your warehouse
{
"event": "message.delivered",
"id": "evt_01HZKQ7T2M",
"message": "msg_01HZKQ6R8P",
"template": "verify-code",
"to": "ada@customer.io",
"smtp": {
"code": 250,
"detail": "2.0.0 OK m18-20020a05622a01d200b004328c7c1234sm"
},
"timestamp": "2026-07-10T00:29:14Z"
}Signed Events, Where You Already Work.
We post delivery, bounce, and complaint events to your endpoint with an HMAC signature and a stable id, so retries stay idempotent. Wire them into your database, your on-call channel, or your product analytics without writing glue code.
- HMAC-signed payloads, always
- At-least-once delivery with automatic retry
- Replay any event from the dashboard
Plain, Legible, Unmistakably You.
Transactional mail is not a marketing campaign. Our templates default to clean typography, a visible sender, and a subject line the recipient can find again a week later. No banner graphics, no dark patterns, no tracking pixels forced on.
- Sender name and reply-to under your control
- Plain-text alternative on every send
- One-click unsubscribe for opt-in categories
Your verification code is 418205
Enter this code in the browser tab you just opened. It expires in ten minutes. If you didn't request it, you can ignore this message.
Signed with DKIM. Sent over TLS. Never resold, never batched with marketing.
From the guides.
Field notes on the standards, patterns, and habits behind mail that actually arrives.
- February 11, 2026
SPF, DKIM, And DMARC Explained For Developers
A practical, RFC-grounded walkthrough of the three email authentication standards every transactional sender has to get right.
Read guide → - March 4, 2026
Magic Links Vs Verification Codes: Which To Send
The developer's guide to picking between a magic link and a six-digit code: security, UX, and the deliverability tradeoffs.
Read guide → - February 18, 2026
Gmail And Yahoo Sender Requirements: What Changed In 2024
The February 2024 Gmail and Yahoo bulk sender rules, what they enforce, and how they apply to transactional email in 2026.
Read guide →
Send Your First Verification Code Today.
Free to start. Fair prices as you grow. No sales call required.