Work from a reviewed draft.
A broadcast connects its audience and published template to one campaign record. Confirm recipient eligibility and account readiness before execution.
Read the broadcast lifecycle ↗EmailBroadcasts
Email broadcasts.
From draft to their inbox.
Create and manage email campaigns through the dashboard, API, CLI, or MCP. Let your team and tools work with the same broadcast and lifecycle.
One campaign. Every way you work.
Prepare a campaign in the dashboard or through your tools. Preview the email, choose when it goes out and follow the result from the same broadcast.
SAME ID / SAME STATEdraft
Email / Broadcasts / The everyday collection eb_01krdgeqcxet5s7t44vh8rt9mg Status: draft
DraftScheduledSentCanceled
Run preflight on the current audience and published template before scheduling. Changing either clears the previous review.
Preflight stopped: publish a reviewed template version before scheduling.
Preflight stopped: no eligible recipients. Inspect membership, preferences and suppressions.
Preflight passed for this example. Sender identity, audience eligibility, allowance and funds need checking again at execution.
Review the current configuration and schedule the example before inspecting completed results.
Scheduled locally. The scheduled record remains editable until sending begins; execution can still fail.
Schedule this example before canceling. Cancellation cannot recall messages already sent.
Canceled before sending in this example. Cancellation does not restore the broadcast allowance.
Two eligible example recipients reached receiver acceptance. Inbox placement, reading and purchase remain unknown.
This completed record cannot be edited or rescheduled. Start a new example draft.
Companies that trust Bird across their communications.
Read Bird customer storiesChoose the workflow. Keep the same campaign.
Build on the public operation.
Use the API when the campaign belongs inside your application. CLI and MCP actions still operate with the account authority and lifecycle of the underlying operation.
Inspect the create operation ↗Campaigns, with a transactional API's discipline.
Broadcasts are marketing email on the Bird Email API, the same network that carries your transactional mail. You target a single audience, schedule with an explicit timestamp, and cancel a send mid-flight if you have to. One targeting concept, no juggling lists and segments.
Five things a broadcast does.
Draft, target, schedule, cancel, measure.
Draft-first lifecycle.
Create a broadcast as a draft, refine the content, and send it when you're ready.
Audience targeting.
Point a broadcast at a single audience. One targeting field, no stacking lists and segments to reason about.
Send now or schedule.
Send now or schedule a campaign up to a year ahead in the dashboard. Review the audience, published content and sender before committing.
Cancel mid-flight.
Cancel a scheduled or sending broadcast to stop recipients it has not reached. Mail already on its way cannot be recalled.
Per-broadcast analytics.
Delivery and engagement metrics for each broadcast, alongside the rest of your email analytics.
Prepare your first broadcast.
Use the dashboard or API to create the same draft, then review the audience and sender.
Create a draft before you commit to a send.
Create a draft with your verified sender, audience and published template. Review its content and recipients in your workspace before choosing to schedule or send. Replace the example values below with your own; this command does not send the campaign.
broadcast.sh
draft
# Create a draft using your verified sender, audience and published template.
# Replace these example values with IDs from your workspace.
bird email broadcasts create \
--from "Acme News <newsletter@acme.com>" \
--audience-id adn_01krdgeqcxet5s7t44vh8rt9mg \
--template emt_01krdgeqcxet5s7t44vh8rt9mg \
--tag campaign=product-launch
# Review the draft in your workspace before scheduling or sending it.
Create the draft with CLI or MCP, inspect its audience and content, then choose when to send. Read the broadcast result and events after sending.
Targeting that respects consent.
A broadcast targets one audience, and Bird applies your marketing suppressions before it sends. Recipient suppressions and opt-out preferences are checked when sending starts. Keep your audience based on consent, and review the deliverable count before scheduling.
Works with the rest of Email.
Build the list you target on the audiences page, send transactional mail through the same send API, and watch results in email analytics.
The interface changes. The campaign stays together.
A broadcast is a saved campaign with an audience, sender, content and delivery state. Start it in the dashboard, update the draft through the API or ask an agent to prepare it through MCP. The same campaign is available for your team to review and schedule.
Prepare your next campaign
Create campaigns in the dashboard
Write and review a newsletter with your team.
Use the Broadcasts API
Integrate the campaign lifecycle with your application.
Let an agent prepare the work
Use MCP to create a draft, inspect content and read campaign results.
Email guides and answers
Continue with the documentation, learning videos and FAQs.
Broadcasts guide
Follow the documented campaign lifecycle and check the current access requirements.
Email pricing
Review published rates for your expected campaign volume.
Put it into practice.
Continue with the documentation, guides and examples for this topic. Resources are in English.
Watch the guideEmail broadcasts: one email to your whole audienceFollow the learning pathBuild your first integration
Get an implementation briefQuestions about broadcasts
How do I target a broadcast?
Choose one saved audience. Bird resolves its current members when sending begins and applies the relevant suppressions and preferences. A template personalizes the message using each recipient’s registered contact properties.
Can I schedule or cancel a broadcast?
Yes. The dashboard supports sending now or scheduling up to a year ahead, with editing and rescheduling before sending starts. Cancel a scheduled or sending broadcast to stop recipients it has not reached; messages already on their way cannot be recalled.
Is this the same as scheduling a transactional message?
They have different contracts. Broadcasts schedule a campaign for an audience. The messages API schedules inline content from 30 seconds to 30 days ahead and cannot combine scheduled_at with a stored template.
Can I rehearse without mailing my customers?
Create a separate audience containing only documented sandbox addresses. The simulated outcomes exercise delivery events and webhooks without external delivery. Sandbox traffic still uses sending allowance and appears in metrics.
Build the campaign around your audience
Audiences
Your contacts and the audiences you target from a broadcast.
Templates
Stored, versioned email templates, personalized per recipient at send.
Analytics
Delivery by domain, provider and IP, with separate engagement breakdowns.
Email API overview
The full Email API: sending, deliverability, IPs, suppression, analytics, and broadcasts.
Talk to our email team
Build a repeatable campaign workflow.
Discuss how your team creates campaigns, selects audiences and schedules sends. We can help you plan the dashboard and API workflow around it.
Create your account, then draft a broadcast in the dashboard or through the API.