Audience-backed sends
Create audiences, upsert contacts, store merge fields, and fan out one update with an individual record for each recipient.
Send the newsletter without standing up a second marketing stack.
Ship a changelog, launch note, or newsletter to an audience that lives in the same API as your transactional sends. NoticeAPI holds the membership, merge fields, and schedule, then records how the broadcast landed for every recipient.
- 1Create an audienceGroup subscribed contacts by product, newsletter, launch list, or customer lifecycle segment.
- 2Upsert contacts and merge fieldsUse the contacts API to add recipients, update subscription state, and store merge fields such as first name.
- 3Draft or schedule the broadcastWrite HTML or text with merge tags, then send immediately or schedule delivery up to 30 days ahead.
- 4Inspect the fan-outPoll the broadcast until its status flips to sent, then read accepted, delivered, bounced, and unsubscribed counts next to each recipient's timeline.
From audience state to recipient outcomes.
- 1
Create an audience
Group subscribed contacts by product, newsletter, launch list, or customer lifecycle segment.
- 2
Upsert contacts and merge fields
Use the contacts API to add recipients, update subscription state, and store merge fields such as first name.
- 3
Draft or schedule the broadcast
Write HTML or text with merge tags, then send immediately or schedule delivery up to 30 days ahead.
- 4
Inspect the fan-out
Poll the broadcast until its status flips to sent, then read accepted, delivered, bounced, and unsubscribed counts next to each recipient's timeline.
The update fans out. The evidence stays attached.
Membership, merge fields, schedules, unsubscribes, and per-recipient outcomes stay next to the API that sends the message — not scattered across a separate marketing tool.
Read acceptable useAudience
The list is API state
Broadcasts fan out from audience membership, stored merge fields, and the subscription state on each contact.
ContentPersonalize without the export
Insert each contact's first name, last name, and email straight from the audience — no second copy of your customer data to keep in sync.
SafetyUnsubscribes are enforced
Use the merge tag for placement control, or let NoticeAPI append the footer and one-click headers automatically.
Outcome
Every recipient leaves a trail
Delivery, bounce, complaint, suppression, unsubscribe, and tracking events feed broadcast stats and signed webhooks.
The controls around the path.
Draft, schedule, send
Create the draft, schedule or cancel it, or send immediately after quota and domain checks pass.
Unsubscribe handling
Place the unsubscribe merge tag yourself or let NoticeAPI append the footer; one-click headers ship with audience sends.
Recipient-level stats
Delivery, bounce, complaint, suppression, unsubscribe, and optional tracking events land in stats, logs, timelines, and webhooks.
The unsubscribe rules run before your broadcast does.
Audience sends skip unsubscribed and suppressed contacts, attach List-Unsubscribe with one-click support, and share suppressions with your transactional sends — so one bounce protects every message that follows.
Read the implementation.
Questions before you ship.
Can I send newsletters and product updates?
Yes. Broadcasts are built for product updates, newsletters, announcements, and lifecycle messages sent to contacts who opted in — with unsubscribe handling on every send.
Can I schedule a broadcast for later?
Yes. Create a broadcast with scheduledAt, or schedule and reschedule a draft through the broadcast API. Scheduled broadcasts still run domain, quota, recipient-state, and suppression checks at send time.
Can I cancel a broadcast after I schedule it?
Yes. Cancel a scheduled broadcast through the API and it drops back to draft — nothing goes out until you schedule it again or call send.
Test it. Then send for real.
Simulator outcomes are free. Move to a verified domain when the path is ready.