Skip to content
Mailbit

Transactional email API

Email that ships with your code.

Send transactional email with one API call. Signed with DKIM, delivered from mail servers we run ourselves, and every bounce, delay and delivery streamed back to you as a webhook.

$ npm i @mailbit/node

send.ts
import { Mailbit } from "@mailbit/node";

const Mailbit = new Mailbit(process.env.MAILBIT_API_KEY);

const { data, error } = await mailbit.emails.send({
  from: "Acme <hello@acme.com>",
  to: ["user@example.com"],
  subject: "Welcome",
  html: "<p>Hi!</p>",
});

// => { data: { id: "em_7fQk2LmNpR4sTvWx" }, error: null }

Features

Everything you need to send, nothing you have to babysit

Mailbit covers the full lifecycle of a transactional email — from the API call to the final delivery receipt.

REST API + TypeScript SDK

A small JSON API and a typed @mailbit/node client that returns { data, error } instead of throwing.

Batch send

Send up to 100 distinct emails in a single request, ideal for digests and notifications.

Scheduled sending

Pass scheduledAt as an ISO 8601 timestamp, up to 30 days ahead, and cancel any time before it goes out.

Idempotency keys

Retry safely. A repeated Idempotency-Key within 24 hours replays the first response instead of sending again.

Attachments, headers & tags

Attach files as base64, set custom headers, and tag messages so you can filter logs and webhooks.

Domain verification

Per-domain 2048-bit DKIM keys, SPF, a custom return-path subdomain and DMARC guidance.

Signed webhooks

Every delivery event, signed with HMAC-SHA256, retried up to 8 times and recorded in a delivery log.

Automatic suppression

Hard bounces and complaints add the address to your suppression list; suppressed recipients are skipped.

Scoped API keys

Full-access or sending-only keys, optionally restricted to a single domain.

A dashboard that explains itself

Email logs with a per-event timeline, plus domains, API keys and webhooks at app.mailbit.dev.

How it works

From zero to first email in three steps

  1. 01

    Add your domain

    Add the domain you send from and publish the DNS records we generate. We verify them for you.

    TXT  mbk3x9qa._domainkey.acme.com  "v=DKIM1; k=rsa; p=MIIBIjAN..."
    MX   send.acme.com                smtp.mailbit.dev  (10)
    TXT  send.acme.com                "v=spf1 include:spf.mailbit.dev ~all"
    TXT  _dmarc.acme.com              "v=DMARC1; p=none; rua=mailto:dmarc@acme.com"
  2. 02

    Create an API key

    Generate a full-access or sending-only key in the dashboard. Restrict it to one domain if you like.

    # .env
    MAILBIT_API_KEY=mb_…
  3. 03

    Send

    Call the API from any language, or use the TypeScript SDK. You get an email ID back immediately.

    await mailbit.emails.send({
      from: "Acme <hello@acme.com>",
      to: "user@example.com",
      subject: "Your login code",
      text: "Your code is 482913",
    });

Deliverability

Authenticated, filtered and accountable by default

Getting to the inbox is mostly about doing the boring things right, every time. Mailbit does them for you.

DKIM, per domain

Every domain gets its own 2048-bit RSA key. Messages are signed at the edge of our MTA before they leave.

SPF & DMARC alignment

SPF and an MX record live on your return-path subdomain, and we recommend a DMARC record to start monitoring alignment.

Custom return-path

Bounces flow through send.yourdomain.com, so the envelope sender carries your brand, not ours.

Suppression list

Addresses that hard-bounce or complain are added to your team’s suppression list and skipped on future sends.

Outbound filtering

Outgoing mail is scanned by Rspamd, which keeps abusive traffic off the shared infrastructure.

Infrastructure we run

Mailbit sends from our own Postfix MTAs. No resold relays — we own the IPs, the queues and the logs.

Webhooks

Know what happened to every message

Subscribe an endpoint and Mailbit streams delivery events to it as they happen — signed with HMAC-SHA256, retried up to 8 times with exponential backoff, and recorded in a delivery log.

  • email.sent

    Accepted by our MTA and queued for delivery.

  • email.delivered

    The receiving server accepted the message.

  • email.delivery_delayed

    Temporarily deferred; we keep retrying.

  • email.bounced

    Permanently rejected. The address is suppressed.

  • email.complained

    The recipient marked it as spam.

  • email.failed

    Could not be sent, with a failure reason.

incoming webhook
POST /webhooks/mailbit HTTP/1.1
webhook-id: msg_4Lx7NpQz2KcWm9Ts
webhook-timestamp: 1763290800
webhook-signature: v1,K5oZfzN95Z9UVu1EsfQmfVNQhnkZ2pj9o9NDN/H/pI4=

{
  "type": "email.delivered",
  "createdAt": "2026-11-16T10:20:00.002Z",
  "data": {
    "emailId": "em_7fQk2LmNpR4sTvWx",
    "from": "Acme <hello@acme.com>",
    "to": ["user@example.com"],
    "subject": "Welcome",
    "tags": [],
    "createdAt": "2026-11-16T10:19:58.120Z",
    "recipient": "user@example.com"
  }
}

Signatures follow the Standard Webhooks scheme: an HMAC-SHA256 over id.timestamp.body. Verify them in one line with verifyWebhook() from the SDK.

Pricing

Simple pricing that grows with you

Start free. Upgrade when your volume does.

Free

$0/mo

For side projects and trying things out.

  • 3,000 emails / month
  • 1 domain
  • REST API & SDK
  • Webhooks
  • Email logs
Request access
Popular

Pro

$20/mo

For production apps with real users.

  • 50,000 emails / month
  • Multiple domains
  • Batch & scheduled sending
  • Scoped API keys
  • Longer log retention
Request access

Scale

Custom

For high volume and specific requirements.

  • Volume pricing
  • Higher rate limits
  • Priority support
  • Custom log retention
Contact us

Send your first email in minutes.

Mailbit is in private beta. Ask for an invite and we'll set you up.