Reliable email delivery
for modern applications

Optimize your transactional email workflows with secure, scalable, and developer-friendly delivery for OTPs, password resets, receipts, alerts, and notifications from your verified domain.

API & SMTP
Verified domains
Signed webhooks

How delivery works

From your app to the inbox, fully observable

Your application hands the message to IBEE over API or SMTP. IBEE sends it from your verified domain and reports every delivery event back to you.

Delivery path

live

Delivery events

sample stream

delivereda•••@example.comotpnow
deliveredd•••@example.comlogin-alert2s ago
deliveredp•••@example.ininvoice4s ago
sents•••@example.iootp6s ago
bouncedt•••@example.netwelcome8s ago
deliveredm•••@example.comalert10s ago

Get started

Four steps to your first email

No mail servers to run. Add a domain, prove you own it, create a token, and send.

Step 1

Add your domain

Use a domain or subdomain you control.

mail.yourcompany.com

Step 2

Verify DNS records

Publish the records IBEE generates.

TXT · SPF · DKIM

Step 3

Create a send-only token

Scoped to your verified domains.

ibee_em_••••3f9a

Step 4

Send your first email

Call the API or connect over SMTP.

delivered

Why IBEE Email Service?

IBEE Email Service is a transactional email service that integrates into any application over API or SMTP. Add your sending domain, verify it with DNS records, and send OTPs, password resets, receipts, alerts, and notifications under your own brand. Send-only tokens keep application access scoped, signed webhooks report every delivery event back to your systems, and one dashboard tracks emails sent, delivery rate, bounce rate, and active domains — without running your own mail infrastructure.

Built for developers

Send with a few lines, over API or SMTP

Call the API from your backend, or point an existing SMTP client at IBEE. Either way, you authenticate with a send-only token and send from your verified domain.

Backend services and APIs
Background workers and queues
Automation jobs and CI/CD pipelines

1curl -X POST "$IBEE_EMAIL_ENDPOINT" \
2  -H "Authorization: Bearer $IBEE_EMAIL_TOKEN" \
3  -H "Content-Type: application/json" \
4  -d '{
5    "from": "no-reply@mail.yourcompany.com",
6    "to": "customer@example.com",
7    "subject": "Your verification code",
8    "html": "<p>Your code is <b>482917</b></p>"
9  }'

Illustrative example — see the documentation for the exact endpoint and request fields.

Use cases

Every email your product sends

The messages users are waiting for — sent from your domain, the moment your app triggers them.

482917

OTP and login emails

Send verification codes, login alerts, and account authentication emails.

Password resets

Deliver secure account recovery emails from your verified domain.

Order confirmations

Send receipts, purchase confirmations, invoices, and payment updates.

Application alerts

Notify users about system events, workflow changes, and security activity.

Product notifications

Send onboarding emails, status updates, usage alerts, and account messages.

on: deploy.succeeded→ email.send(team)✓ queued ▍

Developer workflows

Trigger emails from backend services, workers, automation jobs, and CI/CD flows.

Visibility

Know what happened to every message

Track emails sent, delivery rate, bounce rate, and active domains from one dashboard — and stream delivery events to your own systems with signed webhooks.

Email activity

livesample data

Emails sent

Delivery rate

0.0%

Bounce rate

0.0%

Active domains

Sending volume · live volume

Sending domains

mail.yourcompany.com verified
notify.yourcompany.com verified
billing.yourcompany.com verified
alerts.yourcompany.com verified

Webhook

signed

POST https://yourapp.com/hooks/email
signature: t=…, v1=5c1e…

{
  "event": "delivered",
  "to": "c•••@example.com",
  "domain": "mail.yourcompany.com"
}

Verify the signature with your webhook secret before trusting an event.

Start sending
transactional emails.

Add your domain, create a send-only token, and integrate email delivery into your application using API or SMTP.

Add Domain View Documentation

Frequently Asked Questions

IBEE Email Service lets applications send transactional emails from verified domains using API or SMTP.

You can send OTPs, password resets, order confirmations, notifications, application alerts, and other transactional emails.

Yes. You need to add a sending domain and configure DNS records before sending from that domain.

Yes. You can use a domain or subdomain you control, such as email.example.com, without changing your existing website or mailbox setup.

Yes. The service is designed for API or SMTP-based sending depending on your application workflow.

Email tokens are send-only tokens used by your applications to send transactional emails from verified domains.

Yes. You can configure a webhook endpoint to receive signed delivery events in your application.

Yes. The dashboard can show metrics such as emails sent, delivery rate, bounce rate, and active domains.

Have more questions?

Contact Our Technical Team→

Reliable email delivery for modern applications