maya@example.comSendingDelivered
AAcme09:41

Reset your password

Choose a new one. This link expires in 1 hour.

Reset password

Developer-first

Send with your favorite stack.

One API call, or SMTP. Same pipeline.

  • One call

    REST or SMTP. Same guarantees.

  • Idempotent

    Retries never double-send.

  • Scoped keys

    A service can send — and nothing more.

Send an email
curl -X POST 'https://www.unitpost.com/email' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'User-Agent: my-app/1.0' \
  -H 'Content-Type: application/json' \
  -d '{
    "from": "you@yourdomain.com",
    "to": "customer@example.com",
    "subject": "Welcome to Acme",
    "html": "<h1>Hello</h1>"
  }'

Observability

Every message, traced.

Delivered, opened, clicked, bounced. Per email, or in aggregate.

Welcome to Acmeto ada@example.com
  1. Sent09:41:02
  2. Delivered09:41:03
  3. Opened09:44:17
  4. Clicked09:44:25

Drop-in SMTP

Already have an SMTP setup?

Swap host, username, password. Keep your mail code.

  • TLS

    Ports 587 and 465.

  • API key as password

    Rotate or revoke anytime.

Start for free
SMTP relay
Hostsmtp.example.comsmtp.unitpost.com
Usernameyou@example.comunitpost
Password••••••••••Your API key
Port587STARTTLS

Deliverability

Reach inboxes, not spam folders.

Domain auth, then we keep checking it.

  • Domain auth

    DKIM, SPF, DMARC. Copy-paste records.

  • Reputation

    Suppression, idempotency, rate limits.

acme.comPendingVerified
  • DKIM
  • SPF
  • DMARC

Reliability

What a transactional stream needs.

Idempotent, suppressed, in the inbox.

Deliverability

DKIM, SPF, DMARC. Kept in the inbox.

Templates by id

Build once. Send with variables.

Batch & scheduled

Up to 100 per call. Cancel before send.

Per-message tracking

Dashboard and API. What happened to that reset.

Suppression

Bounces and complaints. Automatic.

Rate-limited

Per-workspace limits. Scoped keys.

Extendable

Do more than sending.

One SDK. Send, retrieve, cancel — plus campaigns, webhooks, and domains.

Send an email
curl -X POST 'https://www.unitpost.com/email' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'User-Agent: my-app/1.0' \
  -H 'Content-Type: application/json' \
  -d '{
    "from": "you@yourdomain.com",
    "to": "customer@example.com",
    "subject": "Welcome to Acme",
    "html": "<h1>Hello</h1>"
  }'

Integrations

Works with what you run

Add Unitpost to the tools you already use, or point SMTP at the relay.

Use cases

Transactional and marketing, on the same rails.

From a welcome email to a five-step drip.

Infinite more use cases

Start free

Send your first email in minutes

$0/ mo

  • 5,000 emails / mo — no credit card
  • Your domain with DKIM, SPF & DMARC
  • REST API, SMTP & official SDKs
  • Visual editor + code templates
  • Open & click tracking + signed webhooks
  • 10,000 contacts · automatic suppression

Questions

Common questions

What is transactional email?

Transactional email is mail sent to one person in response to something they did — a password reset, a receipt, an OTP code, a shipping notification. It is distinct from marketing email, which goes to many recipients at once and legally requires an unsubscribe link. Transactional mail is expected by the recipient, so it should never carry a marketing footer.

How do I stop duplicate emails when my code retries?

Send an Idempotency-Key header with the request. Unitpost dedupes on that key for 24 hours, so a retried POST returns the original result instead of sending a second email. Reusing a key with a different body returns 409 rather than silently sending the wrong message. This matters most in webhook handlers and job queues, where at-least-once delivery makes retries normal.

Can I schedule or cancel a transactional email?

Yes. Pass scheduled_at when you send, then PATCH the email to reschedule or cancel it before it goes out. Free plans can schedule up to 7 days ahead; paid plans up to 90. Batch sends can be cancelled as a whole batch.

How do I know whether an email was delivered?

Every message emits events you can read via the API or receive as signed webhooks: sent, delivered, delivery_delayed, bounced, complained, opened, clicked, and failed. Webhook deliveries are svix-compatible, signed with HMAC-SHA256, so you can verify them with any Svix-compatible library.

Do bounces and complaints suppress future sends automatically?

Yes, and you cannot accidentally turn it off. A hard bounce or spam complaint writes a suppression that blocks future sends to that address, and three soft bounces in a row escalate to a suppression too, as does one to a domain that doesn't exist. Complaint suppressions cannot be self-serve deleted — the API returns 409 — because removing one is how senders destroy their own reputation.

Can I send transactional email over SMTP instead of the API?

Yes. Point any SMTP client at smtp.unitpost.com with the username unitpost and an API key as the password. It runs through the same pipeline as the REST API, so tracking, webhooks, suppression, and the dashboard behave identically. STARTTLS on 587, 2587 or 25, implicit TLS on 465 or 2465; TLS is mandatory.