The best
send
experience

For
every
application

One API for the four messages your product actually has to deliver. Email, SMS, WhatsApp, and verification codes from your own domain, your own sender ID, your own brand.

Get started Read the docs

Everything you need

Four channels.
One auth surface.

Your brand in every inbox

Live

Email

Send password resets, magic links, receipts, and notifications from your own domain. Every header reads as your brand. Every reply lands back with you, not us.

Reach every phone, one API

Live

Send transactional SMS through regional carriers behind one endpoint. Nigerian numbers route the cheapest way, international numbers route the most reliable way, and you write the same line of code either way.

Meet customers where they actually read

Beta

Send OTPs, order updates, and ticket replies through WhatsApp Business. We handle the template approvals, the rate-limit handshake, and the 24-hour service window. You call one endpoint.

OTP without the boilerplate

Live

Verify

Start a verification challenge with one POST, check it with another. Throttling, expiry, attempt limits, and channel fallback are built in. The bits every team rewrites the first time.

One API

Same auth.
Same envelope.
Three endpoints.

The hardest part of a multi-channel send pipeline is maintaining three SDKs that each model "delivered" a slightly different way. We collapsed them.

Idempotency keys on every send
Test + live keys with one promotion step
Signed webhook events with replay protection

Email SMS Verify curl · v1

curl -X POST https://api.zevsend.com/v1/emails \
  -H "Authorization: Bearer zs_live_***" \
  -H "Idempotency-Key: 8a7c5f00-..." \
  -H "Content-Type: application/json" \
  -d '{
    "from": "security@acme.com",
    "to": "jane@example.com",
    "subject": "Your Acme sign-in link",
    "html": "<p>Tap to sign in...</p>"
  }'

curl -X POST https://api.zevsend.com/v1/sms \
  -H "Authorization: Bearer zs_live_***" \
  -H "Idempotency-Key: 8a7c5f00-..." \
  -H "Content-Type: application/json" \
  -d '{
    "from": "ACME",
    "to": "+2348100000000",
    "body": "Your Acme code is 482310. Expires in 5 min."
  }'

curl -X POST https://api.zevsend.com/v1/verify/start \
  -H "Authorization: Bearer zs_live_***" \
  -H "Content-Type: application/json" \
  -d '{
    "channel": "sms",
    "to": "+2348100000000",
    "length": 6,
    "expires_in": 300
  }'

How it works

Verify.
Mint.
Send.

Verify your sending domain

Add the DKIM, SPF, and MAIL FROM records we generate. BYO-DKIM by default, so the DNS your customers inspect references zevsend, never the upstream carrier.

TXT zevsend._domainkey v=DKIM1;p=...

Mint an API key

Test keys send only to your verified-recipients allowlist. Live keys unlock once a human reviews your domain, so spammers stay out without slowing real teams down.

zs_live_8aB...e3F

Send

One POST per message across all four channels. Webhooks fire on delivery, bounce, complaint, open, and click. Same envelope shape regardless of channel.

✓ email.delivered

Trust and compliance

How we keep
the inbox open.

zevsend is built for transactional messages only: receipts, password resets, magic links, OTPs, and the notifications a user explicitly asked for. No broadcasts, no marketing blasts, no list-rental. The commitments below are how we keep deliverability high for everyone on the platform.

Acceptable Use Privacy Report abuse

Transactional only

Customer terms forbid bulk, marketing, and acquired-list sending. Violations get the account suspended, not throttled.
Bounce and complaint feedback

Bounced or complained addresses move to a per-team suppression list automatically and never get re-sent to.
Admin go-live review

New teams start in sandbox, sending only to a verified-recipients list. A human reviews the team's domain before live keys are issued.
One-click unsubscribe

Every email carries a List-Unsubscribe header. Customer terms require unsubscribes be honoured within 24 hours.
Per-team rate limits

API throttling and daily quotas enforced at the gateway. A noisy customer cannot drown out the platform.
Reachable humans

Abuse reports go to abuse@zevsend.com. Security disclosures to security@zevsend.com. We reply.

Part of the Zev family

One identity.
Many products.

Every product in the Zev family signs in with one account. If you already have a zevcloud domain, zevsend can publish your sending records for you in one click.

You are here

zevsend

Transactional messaging for the four message types every product has to deliver. Built to read like your brand, land in the inbox, and stay out of your way.

Live