Verify domain → Create key → POST JSON
Send email they trust.
Verify a domain, create a key, and send. Your existing mailboxes stay untouched.
- No MX migration
- Domain-scoped API keys
- Queued, processing, sent, failed
Sending-only mail. Keep inboxes where they are.
Use your own app, your own HTTP client, your verified domain.
Host api.resendermail.com X-API-Key ep_live_… { "from": "hello@yourdomain.com", "to": ["billing@acme.com"], "subject": "Receipt" } 200 OK { "id": "em_4f2c…", "status": "queued" }
FOR
The emails people wait for.
Transactional mail by default. Optional hosted mailboxes need MX to mail.resendermail.com. No newsletters, no customer SMTP relay.
Receipts, resets, invoices, and alerts share one job: leave your product fast, clearly, and from the right domain.
-
Password resets
Auth links that have to land.
-
Receipts
Order and payment confirmations.
-
Invoices
Bills and statements from your product.
-
Alerts
OTP, security, and status notices.
INTEGRATE
Three steps. Then send.
Verify a sending domain, create a domain-scoped key, and POST JSON from cURL, Node, Python, .NET, Java, or Go.
Copy the payload, switch languages, and see the same API model every client gets back: an id plus the first delivery state.
- Use your own HTTP client
- One request returns an id
- Track queued, processing, sent, or failed
curl -X POST https://api.resendermail.com/api/v1/emails \
-H "X-API-Key: ep_live_..." \
-H "Content-Type: application/json" \
-d '{
"from": "hello@yourdomain.com",
"to": ["customer@example.com"],
"subject": "Hello from ResenderMail",
"html": "<p>Hello</p>"
}' AUTHENTICATED
Sending-only DNS.
Four TXT records. No MX change. Inboxes keep living where they already are.
- Queued Returned with an id
- Processing Worker picked it up
- Sent Handed to the relay
- Failed Did not leave the relay
All records stay on the sending domain. Your inbox provider does not move.
SPF
Authorize outbound mail
DKIM
Sign every message
DMARC
Policy for unauthenticated mail
Ownership
Prove you control the domain
Exact hosts and values come from the dashboard after you add a domain.
ACTIVITY
Every send has an id.
The dashboard lists messages. GET /api/v1/emails/{id} returns queued, processing, sent, or failed. Send a test without leaving the app.
| Id | To | Subject | Status |
|---|---|---|---|
| em_8c1a | ava@acme.com | Reset your password | Sent |
| em_4f2c | billing@acme.com | Receipt | Processing |
| em_91de | ops@acme.com | Invoice 1842 | Sent |
| em_2b07 | lea@example.com | Sign-in code | Failed |
WHY RESENDERMAIL
Built for sending.
Local currency, no mailbox move, and keys that cannot leap domains.
-
KES and USD, independently
Local and USD catalog prices — not a converted rate. Pay in the currency you choose.
-
Zero MX migration
Send from a subdomain. IMAP, webmail, and existing mailboxes keep working.
-
Domain-scoped API keys
Each key is tied to one verified domain. Compromise stays contained.
-
Sender identities
From addresses live on the verified domain. They are send aliases, not hosted mailboxes.
WORKSPACE
The app around the API.
The dashboard keeps the operational layer close to the API: test sends, teammates, and billing without bloating the sending path.
Open the dashboardPick a verified identity and fire a message from the dashboard.
- From
- hello@yourdomain.com Verified
- To
- you@yourdomain.com
- Subject
- Test send
Illustrative workspace. The live app uses these same surfaces.
FAQ
What this is. What it is not.
Email supportThis product sends transactional mail. The FAQ keeps the boundaries explicit so the homepage does not overclaim.
Do you offer SMTP or SDKs?
No. Send with POST /api/v1/emails and X-API-Key. Use fetch or your own HTTP client. There is no customer SMTP relay.
Can I send newsletters or host inboxes?
No newsletters or marketing ESP features. Sending stays API-only by default. Optional hosted mailboxes (dashboard Inbox + IMAP/SMTP) require enabling mailbox hosting and pointing MX at mail.resendermail.com.
What status can I look up?
GET /api/v1/emails/{id} returns queued, processing, sent, or failed. The dashboard shows the same timeline. Opens, clicks, and inbox bounces are not tracked yet.
START HERE
Start sending tonight.
Verify a domain, create a key, and POST. Keep your existing mailboxes.
- Verify a domain
- Create a key
- POST /api/v1/emails