Email deliverability
Land in the inbox, not the spam folder.
Deliverability is whether your email reaches the inbox at all. Bird signs every message, warms your IPs automatically, suppresses bad addresses before they cost you reputation, and watches the major blocklists. The mail you send is the mail that lands.
import { BirdClient } from "@messagebird/sdk";
import { render } from "@react-email/render";
import { WelcomeEmail } from "./emails/welcome";
const bird = new BirdClient({ apiKey: process.env.BIRD_API_KEY! });
const { data, error } = await bird.email.send({
from: "Bird <hello@bird.com>",
to: ["ada@example.com"],
subject: "Your invite is ready",
html: await render(<WelcomeEmail name="Ada" />),
}).safe();
if (error) throw error;
console.log(data.id);
// → "em_2bX91Yk8h..."You can sign in any time at bird.com/login.
Your test API key is on your dashboard, ready to send.
Deliverability is a feature, not a hope.
Every account on the Bird Email API gets the primitives below: authenticated sending, managed IP warmup, automatic suppression, and live blocklist monitoring. You don't wire them together yourself. Zillow lifted email open rates 161% after moving deliverability onto Bird.
Five things working for you on every send.
On every send, with no setup step and no add-on SKU.
- 01
Authenticated sending.
DKIM, SPF, and DMARC signed for every verified sending domain, with optional BIMI support. DNS usually verifies within minutes of publishing the records.
- 02
Managed IP warmup.
Start on a shared pool, or take dedicated IPs that Bird warms automatically over roughly 30 days and organizes into pools you control.
- 03
Automatic suppression.
Bounces, complaints, and unsubscribes suppress the recipient automatically and reversibly, so a bad address never burns your reputation twice.
- 04
Blocklist monitoring.
Live monitoring across the major DNSBLs surfaces a reputation problem early, while you can still act on it.
- 05
Per-provider visibility.
Bounce codes, complaint types, and mailbox-provider and client breakdowns, broken out per domain, ISP, and IP, in the dashboard and via the stats API.
You don't write deliverability. You watch it.
Signing, warmup, and suppression are automatic. What you get on top is visibility: pull bounce and complaint rates, mailbox-provider breakdowns, and bounce codes from the stats API, and alert on a trend before it costs you the inbox.
// Watch the rates that decide whether you reach the inbox.
const { data } = await bird.email.stats.summary({
from: "2026-06-01",
to: "2026-06-23",
}).safe();
console.log(data.bounce_rate); // 0.004
console.log(data.complaint_rate); // 0.0006
console.log(data.delivered_count); // 248119What healthy sending looks like.
Bird weighs your bounce and complaint rates against volume and history, then acts: healthy traffic sends unthrottled, a degrading reputation gets throttled, and harmful signals pause sending before they torch your domain. As a rule of thumb, hard-bounce rates approaching 5% trigger a pause and healthy lists run well under 1%. Gmail and Yahoo enforce a 0.3% complaint ceiling for bulk senders, and sustained rates above ~0.1% already hurt placement.
Go deeper in the docs.
Set up authentication with the DKIM, SPF & DMARC guide, plan a ramp with the IP warmup guide, or read the full deliverability guide for the playbook end to end.
Deliverability FAQ
What is email deliverability?+
Do I need a dedicated IP for good deliverability?+
How does Bird handle bounces and complaints?+
How do I know if my deliverability is slipping?+
The rest of the Email platform
One API, one set of keys. Explore the other capabilities.
About 40% of the world's commercial email already runs on Bird.
Transactional and marketing email on infrastructure we've run for a decade. Deliverability is one capability of the Bird Email API: sending, dedicated IPs, suppression, and analytics ship with it.