Formerly SparkPost
SparkPost is now Bird Email.
SparkPost is part of Bird. For a new project or a planned migration, explore Bird Email: sending, templates, audiences, broadcasts and delivery reporting in one platform. Review the API, domain records and event handling before moving an existing integration.
Create an account for a new Bird project. Discuss an existing SparkPost integration with your account team.
Your next email project
SparkPost → Bird
Existing integration
SparkPost
Review before moving traffic.
New project
Bird Email
Build with Bird’s API and SDKs.
A planned migration, step by step
Map the integration
API calls · templates · events
Prepare the sender
Domain records · suppressions · IPs
Test before cutover
Message content · delivery · webhook handling
Illustrative migration checklist. Review an existing SparkPost integration with your account team before planning a move.
What happened to SparkPost?
SparkPost is part of Bird. For a new project, Bird Email brings sending, campaigns and delivery reporting into the wider Bird platform. For an existing SparkPost integration, plan the move explicitly: review API calls, domain records, templates, suppressed recipients and webhook handling with your account team before switching traffic.
What you get now that
SparkPost is Bird Email.
The deliverability you trusted,
on a modern multichannel API.
- 01
Delivery controls for your next integration.
DKIM signing, SPF alignment, DMARC policy setup, managed IP warmup and recipient suppressions. Explore the controls and delivery signals in Bird deliverability.
- 02
One API for every channel.
The same send call, auth model, error envelope, and webhook shape for email, SMS, WhatsApp, and voice. A verification code can start as email and fall back to SMS without a second vendor.
- 03
Modern SDKs and React templates.
SDKs in every major runtime. Pass raw HTML, or render a React Email template and we build the MIME at send time.
- 04
Managed dedicated IPs.
Dedicated IPs provisioned per account and warmed automatically over roughly 30 days, in pools you control.
- 05
Deliverability analytics, broken down.
Delivery, bounces, complaints, opens, and clicks per domain, ISP, and IP, in the dashboard and through the stats API.
- 06
Signed webhooks for every event.
HMAC-signed, replay-protected, and idempotent. The same signed envelope across every channel, so one handler parses them all.
The send, today.
Here is a send on the current Bird Email API.
Typed SDKs in TypeScript, Python, Go, and PHP, a curl example, and the CLI. The first send can go to a sandbox address (delivered@messagebird.dev), so you can build against the live API before you verify a domain.
const msg = await bird.email.send({
from: { email: "onboarding@messagebird.dev", name: "Bird" },
to: ["delivered@messagebird.dev"],
subject: "Hello from Bird",
html: "<p>My first Bird email.</p>",
});
console.log(msg.id, msg.status); // "em_…", "accepted"Who it is for
Bird Email is built for teams that send across channels. If you only ever send email and will never touch SMS, WhatsApp, or voice, the multichannel platform is more than you need. The email API still stands on its own, and pricing is usage-based, so you only pay for what you send.
Put it into practice.
Continue with the documentation, guides and examples for this topic. Resources are in English.
Questions about SparkPost and Bird
What happened to SparkPost, and do I have to migrate?
Is the API the same as SparkPost's?
Explore the Email platform
The SparkPost engine, now one API. Each capability in depth.
Start your next project. Plan your next move.
Build a new project with Bird Email, or review an existing SparkPost integration with your account team before planning a migration.
Create an account for a new Bird project. Discuss an existing SparkPost integration with your account team.