Email

Transactional and bulk email, combined with SMS in one API

REST or SMTP, high deliverability, and a fallback to SMS when an email bounces — all from the same account as your other channels.

Order confirmation
Illustrative
One account

Email is the one channel most teams still run alone.

SMS, WhatsApp and chat live in one platform — email is the exception. A separate vendor, a separate dashboard, a separate bill, for a message that’s often the exact same one.

Your stack · this monthIllustrative
  • SMS
  • WhatsApp
  • Web chat
  • Emailrun alone

Email sits outside: its own dashboard, its own bill.

2
Vendors
2
Dashboards
2
Bills

On SMSLocal, email is one more line on the same account: one vendor, one dashboard, one report.

One API

One API for email and SMS

Try it: flip the switch, then send, and watch where the message actually lands.

POST /v1/sendREST · SMTP
  1. Request accepted
  2. Email delivered
  3. Email opened

Press “Send test email” to watch the events arrive.

Two kinds of email

Transactional and bulk, on one API

Pick the kind that fits the message. Both send over REST or SMTP, with fallback through the SMS API.

Triggered by something a person just did in your product, sent to them alone, right away.

  • Order confirmation
  • Password reset
  • OTP email
  • Receipt
  1. 1Event in your app
  2. 2REST API or SMTP
  3. 3One email, at once

From a single OTP email…

The same API and the same account handle both.

How it works

Start sending email in three steps

  1. 1

    Verify your domain

    Add a few DNS records — SPF, DKIM and DMARC — we walk you through it.

    • SPF
    • DKIM
    • DMARC
  2. 2

    Design your templates

    Build transactional and bulk templates visually, or send raw HTML via API.

    • Visual builder
    • Raw HTML via API
    • Transactional
    • Bulk
  3. 3

    Send with fallback on

    Launch sends that automatically retry over SMS on a bounce or no-open.

    • Retry over SMS
    • On a bounce
    • On no-open
Why us

Why teams send email through SMSLocal

  • 01

    High deliverability

    Managed sending infrastructure and reputation monitoring keep you out of the spam folder.

  • 02

    A real fallback channel

    Bounces and unopened sends can automatically retry over SMS — nothing just disappears.

  • 03

    One report, two channels

    See email and SMS delivery, opens and clicks side by side in the same dashboard.

  • 04

    Built for scale

    From a single OTP email to a million-send campaign, the same API handles both.

Ecosystem

Email fits right into your messaging stack

Pair email with SMS, WhatsApp and agentic AI across the same customer record.

Deliverability

Email authentication, explained

Three DNS records (SPF, DKIM and DMARC) tell inbox providers your mail is really yours. We walk you through adding them.

Example DNS record Verified
Type
TXT
Host
@ (yourbrand.com)
Value
v=spf1 include:_spf.sender.example ~all
Without SPF

Inbox providers cannot tell your mail from a forgery, so more of it is doubted.

Placeholders only. Your real values come from the setup.
Get Started

Send email that has a backup plan

One API for email and SMS — set up your first send in minutes.

Answers To Your Questions

Email API — frequently asked questions

Transactional and bulk email sending via REST API or SMTP relay, template design, deliverability monitoring, and reporting — combined with SMS in the same account.

Yes — point your existing SMTP relay at us with no code changes, or integrate directly with the REST API for more control.

A bounce or unopened send can automatically trigger a fallback SMS to the same contact, so the message still reaches them.

Yes, email and SMS run on the same API and account, with combined delivery, open and click reporting in one dashboard.