Keep your template workflow.
Send HTML, render React Email in your application, or use a stored template. Keep the workflow your team knows.
Explore email templates ↗ BIRD EMAIL / TRANSACTIONAL EMAIL AT SCALE
Your email API.
Built for what’s next.
Send receipts, password resets and account updates with Bird’s API.
Track delivery, investigate failures and scale with your email team.
A FEW LINES OF CODE. A REAL CONNECTION.BIRD / EMAIL
content.mts
Save beside send.mtsimport { readFileSync } from "node:fs";
export const html = readFileSync(
new URL("./welcome.html", import.meta.url), "utf8",
);
export const attachments = [{
filename: "shoreline.webp",
content_id: "shoreline",
content: readFileSync(
new URL("./shoreline.webp", import.meta.url),
).toString("base64"),
}];
send.mts
npm install @messagebird/sdk tsxnpx tsx send.mtsimport { BirdClient } from "@messagebird/sdk";
import { html, attachments } from "./content.mts";
const bird = new BirdClient({ apiKey: process.env.BIRD_API_KEY! });
const msg = await bird.email.send({
from: { email: "onboarding@messagebird.dev", name: "Fieldnotes" },
to: [{ email: "delivered@messagebird.dev", name: "Alex Lee" }],
subject: "A beautiful beginning.",
category: "transactional",
html,
attachments,
});
console.log(msg.id, msg.status);
welcome.html
Save beside send.mts<div style="background:#f8f9f1;color:#171c19;font-family:Arial,sans-serif">
<div style="padding:30px 24px">
<p style="margin:0 0 26px;font-size:18px;letter-spacing:-1px">fieldnotes.</p>
<p style="margin:0 0 20px;font-size:42px;font-weight:700;line-height:1.05;letter-spacing:-2px">
Good things<br>start here.
</p>
<p style="font-size:14px;line-height:1.65">
Hi Alex. Your Fieldnotes account is ready.<br>We’re glad you’re here.
</p>
<a href="https://example.com/account" style="display:inline-block;margin-top:18px;color:#171c19;font-size:13px;text-decoration:none">
Open your account ↗
</a>
</div>
<img src="cid:shoreline" alt="A quiet Mediterranean shoreline" width="840" style="display:block;width:100%;height:auto">
</div>
f.
FieldnotesTo: Alex Lee ⌄
A beautiful beginning.
fieldnotes.
Good things
start here.
Hi Alex. Your Fieldnotes account is ready.
We’re glad you’re here.
✓Example welcome email delivered.
- 01 Accepted
- 02 Delivered
- 03 Webhook received
This preview uses the HTML in welcome.html. Download the example and set BIRD_API_KEY to run on Node.js 20.3+. Sandbox delivery is simulated; nothing is sent from this page.
Companies that trust Bird across their communications.
A real customer result200MEmails per month, on averageReported by Zillow in its customer story, after migrating to Bird in 2015.Read Zillow’s story
01 / THE EMAIL APITransactional email.
Transactional email.
Ready for your product.
Send welcome messages, password resets and receipts. Trace each message when your customer or support team needs an answer.
Send your first emailRetry without a duplicate send.
Reuse an idempotency key when a request needs a retry. Follow the documented replay window and recovery steps for uncertain results.
Read the idempotency guide ↗Keep your application informed.
Use delivery events and webhooks to connect what happened to an email with what your application does next.
Integrate delivery events ↗Already have an SMTP integration?Connect it to Bird’s SMTP relay Need replies too?Explore inbound email
02 / SDKs & QUICKSTARTS
Email SDKs & quickstarts.
Choose your stack, install the SDK and send to a sandbox recipient. Each quickstart covers setup, the request and its result.
Explore the email docsNext.js
Server actions. Your first send.
Open the quickstart ↗Node.js
Modern JavaScript. A direct integration.
Open the quickstart ↗Python
A typed SDK. Synchronous quickstart.
Open the quickstart ↗Go
A small start in your existing stack.
Open the quickstart ↗Keep the returned message ID, then read the message and follow delivery events. An accepted send confirms that Bird queued the email; delivery is reported separately.
Find your framework
Go straight to a working email example for your application.
Evaluating a stack before you integrate?
See how Bird fits your application, with runnable examples and implementation choices.
ALREADY SENDING SOMEWHERE ELSE?
Switch to Bird.
Bring your templates, domains, and sending requirements.
Follow a migration guide and plan the switch.
FROM REQUEST TO RESULT
Follow every email.
Answer “where is my email?” with a message ID and delivery evidence. Try a successful send, then a hard bounce to see what your team can do next.
Message inspectorONE MESSAGE / THREE VIEWS
Interactive example data. No request is made to Bird.
RECIPIENT OUTCOMEDelivered
The receiving server accepted it.
Delivered means the receiving server accepted the message. It does not establish inbox placement or a human open. This sandbox example simulates that outcome.
Inspect the API payload
Event body · example data
{
"type": "email.delivered",
"timestamp": "2026-09-17T10:00:02.000Z",
"data": {
"email_id": "em_01ky7qc398fmxraqtxn604zeq9",
"recipient_id": "er_01ky7qc398fmwsc96nt6anrbqs",
"workspace_id": "ws_01ky7m21hjffh9s8kq76gyb1xf",
"recipient": "delivered@messagebird.dev",
"recipient_role": "to",
"tags": null,
"metadata": null,
"broadcast_id": null
}
}EMAIL INFRASTRUCTURE IN PRACTICE
Read the story ↗A reported customer result.An email integration in one week.
Iterable’s published story reports onboarding in one week and approximately 1,000 messages per second via API, with detailed deliverability analytics. A historical result from Bird’s email infrastructure.
03 / DELIVERABILITY & INSIGHTSEmail deliverability.
Email deliverability.
Understand each send.
Authenticate your sending domain, monitor delivery events and investigate inbox placement. Give your team a clear path from setup to troubleshooting.
Explore deliverabilityEmail / Sending healthExamplemail.fieldnotes.exampleSending domain
✓ VerifiedSPF✓ Configured
DKIM✓ Verified
DMARC✓ Configured
A CUSTOMER SAYS THEIR EMAIL IS MISSING
Delivered. What next?
- 01Check the message event
Delivered means the receiving server accepted the message.
- 02Check inbox placement separately
Review spam placement and authentication. A delivery event cannot tell you which folder received the email.
- 03Investigate before sending again
Use the message ID and recipient details to trace the issue with your team.
Welcome emailDelivered
Order confirmationDelivered
Invalid recipientSuppressed
When the right home appears,
the email needs to follow.
Read Zillow’s story 200M
emails per month,
reported in Zillow’s story.
FROM YOUR FIRST SEND TO ENTERPRISEEmail API pricing.
Email API pricing.
Room to grow.
Start with a sandbox send, then choose a plan for your volume. Plan a larger rollout with our email team.
START WITH A PUBLISHED PLAN
A clear starting point.
- Free
- US$ 0USD / month
1.000 emails included monthly
- Startup
- US$ 15USD / month
50.000 emails included monthly
Starting monthly plans in USD. Free is capped; paid plans have overage. See all volumes, currencies, limits and add-ons in pricing.
FOR LARGER SENDING OPERATIONSYour volume.
Your volume.
Your requirements.
Review sending peaks, IP strategy and migration with our email team. Bring your security questionnaire and support requirements to the same conversation.
- Sending workload
- Monthly volume and peaks
- Deliverability
- Domains and IP requirements
- Procurement
- Security, DPA and support terms
MORE OF YOUR BUSINESS. ONE PARTNER.Start with email.
Start with email.
Build on Bird.
Add campaigns, inbound replies or another channel when your product needs them. Connect email, WhatsApp and SMS around the same customer and their choices.
Explore all products Fieldnotes / Customer journeyIllustrative workflowTHURSDAY / THE CONFIRMATION
f.
FieldnotesTo: Alex Lee ⌄
Your studio visit is confirmed.
fieldnotes.YOUR STUDIO VISIT / FN–1042A little time
A little time
by the sea.
Hi Alex, your coastal studio visit is booked for Friday at 14:00.
Friday, 14:00Fieldnotes Studio · 1 guest
Email confirmation · booking FN–1042
Build the email confirmation ↗An example you can build with Bird’s APIs. Your application connects customer identity, booking data, and consent across channels.
06 / A GOOD NEXT STEP
The email resource library Email guides and tools.
EXPLAINED
Understand the Email API.
What an email API does, and where it fits in your application.
EVALUATE
Choose your email provider.
Compare the sending workflow, operational controls and costs that matter to your team.
TECHNICAL GUIDE
Handle opt-outs and bounces.
Keep suppression handling connected to the way your application sends.
PRODUCTION CHECKLIST
Prepare for production.
Review transactional email practices before real customers depend on every send.
Can I try the API before verifying a domain?
Yes. Use the shared onboarding sender and sandbox recipients to test your integration. Verify your own domain before sending to customers. Onboarding recipient and daily limits apply. Follow the first-email quickstart.
Can I send transactional and marketing email?
Yes. Bird supports both application-driven messages and marketing email. Choose the appropriate message category and respect consent, unsubscribe, and suppression requirements. Choose the message category.
Can I use React Email or my existing templates?
You can render React Email templates to HTML in your application and send the result through Bird. You can also send your own HTML or use stored email templates. Explore templates.
What limits should I plan around?
Plan for monthly volume, request rate and peak sending, as well as domain and webhook limits. A sandbox test does not establish your production throughput. Read rate limits and retry behavior.
Do I need a dedicated IP?
No. Shared IPs are the default. Dedicated IPs are a paid option for senders with consistent volume and require warmup. Review your plan’s eligibility and sending pattern before choosing one. Understand dedicated IPs and pools.
How do we review security and support?
Use Bird’s Trust Center for security evidence and review the DPA with your team. Confirm support coverage, escalation and any service commitments in your agreement before rollout. Explore enterprise email · Start your security review.
Where can I find pricing and migration help?
See the email pricing page for current options, and follow the guide for your existing provider. Our team can help you plan around sending volume, infrastructure, and your wider Bird setup. Email pricing · Migration guides.
Can I send several messages in one request?
Submit up to 100 independent messages in a batch. The request validates as a unit; after acceptance, each message has its own delivery outcome. Batching does not guarantee that every recipient receives a message. Read the batch sending guide.
Can I schedule email or attach files?
Schedule inline email content for a future send and cancel before sending begins. Scheduled sending cannot be combined with stored templates. Attach files as base64 and use content IDs for inline images; check the documented size and content-type limits. Plan scheduled sending.
How do I connect a message to my application data?
Use tags to group messages for reporting and metadata for application context, such as an order reference. Follow the documented field limits and avoid placing secrets in either. Compare tags and metadata.
How do I test failures before launch?
Use documented sandbox recipients to exercise delivery outcomes and check your webhook handling. A simulated result tests your integration; it does not establish production delivery or throughput. Exercise sandbox outcomes.
YOUR NEXT CONNECTION STARTS HEREBuild your first send.
Build your first send.
Plan your next million.
Start building today, or review your sending volume, migration and support requirements with our email team.
Explore email pricing