Broadcast email API

Broadcast Email API for Consent-Based Product Updates

NoticeAPI broadcasts let developers send newsletters, product updates, changelogs, and lifecycle messages to opted-in audiences from the same platform that sends transactional email.

Create and send a broadcast
curl -X POST https://www.noticeapi.com/api/v1/broadcasts \
  -H "Authorization: Bearer ntc_xxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "audienceId": "aud_123",
    "from": "Acme News <[email protected]>",
    "subject": "June changelog",
    "html": "<p>Hi {{{FIRST_NAME}}}</p><p><a href=\"{{{UNSUBSCRIBE_URL}}}\">Unsubscribe</a></p>"
  }'

curl -X POST https://www.noticeapi.com/api/v1/broadcasts/brd_123/send \
  -H "Authorization: Bearer ntc_xxxxxxxxxxxxxxxxxxxx"

Audiences and contacts

Create audiences, upsert contacts, store merge fields, and send only to subscribed recipients.

Broadcast draft and send API

Create a draft, review the payload, then fan it out through a send endpoint that checks quota and domain readiness.

Unsubscribe enforced

Broadcasts carry signed unsubscribe links and one-click List-Unsubscribe headers, with an auto-footer if needed.

Per-recipient outcomes

Delivery, bounce, complaint, suppression, and unsubscribe events land in stats, logs, timelines, and webhooks.

How it works

From test send to production traffic.

1

Create an audience

Group subscribed contacts by product, newsletter, launch list, or customer lifecycle segment.

2

Add subscribed contacts

Use the contacts API to add or update recipients and merge fields such as first name.

3

Draft the broadcast

Write HTML or text with merge tags, including the unsubscribe URL when you want placement control.

4

Send and watch outcomes

Trigger send, poll the broadcast, and consume events through the same webhook pipeline as transactional email.

Trust

Marketing email stays consent-based

Broadcasts and automations are built for recipients who opted in. Unsubscribed contacts are skipped automatically, suppressions are shared across sending paths, and unsubscribe handling is not optional.

Implementation links

Build with the shipped docs.

FAQ

Questions developers ask before switching email.

Can I send newsletters and product updates?

Yes, when recipients opted in. Broadcasts are built for product updates, newsletters, announcements, and lifecycle messages with unsubscribe handling.

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 use the same consent, unsubscribe, quota, and domain checks at send time.

Do unsubscribed contacts receive future broadcasts?

No. Unsubscribed contacts are skipped automatically and remain skipped unless they re-opt in.

Start free. Send production after your domain is ready.

Free includes 3,000 production emails per month, a 100/day production cap, and one verified sending domain.