Broadcasts

Broadcasts are campaigns sent to an entire audience (contact list). Create a broadcast as a draft, then send it when ready. In-flight broadcasts can be cancelled.

Lifecycle

draft → scheduled → sending → sent → cancelled

A broadcast can also move to paused if sending is halted partway — for example it reaches your monthly or daily send limit, the sender domain is no longer verified, or platform-wide sending is paused. Resume it by sending again (POST /broadcasts/:id/send) once the underlying issue is resolved — it continues from where it stopped.

Review on early list sends

New accounts can reach 500 recipients by broadcast before we've reviewed the account. Most first campaigns are smaller than that and go out in full, with nothing to do.

If your audience is larger, the first 500 are delivered immediately and the broadcast moves to held with the rest queued behind a quick manual review. You'll get an email when it's released, and the broadcast continues from where it stopped — nothing is lost and nobody is emailed twice. Unlike paused, a held broadcast can't be resumed by sending again; POST /broadcasts/:id/send returns 403 with code BROADCAST_HELD until the review clears.

The same allowance applies to very large POST /emails/batch sends, which return LIST_SEND_HELD on the items beyond it.

This is a one-time step per account, not a recurring limit. It exists so one bad actor can't damage the sending reputation that every customer on the platform shares. If you're on a deadline, email support@eusend.dev and we'll clear it.

API endpoints

curl -X POST https://api.eusend.dev/broadcasts \
  -H "Authorization: Bearer eu_live_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "May Newsletter",
    "audience_id": "550e8400-e29b-41d4-a716-446655440000",
    "subject": "What'"'"'s new in May",
    "from": "newsletter@acme.com",
    "html": "<h1>Hello!</h1><p>Here'"'"'s what'"'"'s new...</p>"
  }'

Send a draft broadcast immediately, or schedule it for a future time by passing scheduled_at. This endpoint also resumes a paused broadcast — it continues from where it stopped, skipping recipients already sent. The audience is set when creating the broadcast. Broadcasts can also be pre-scheduled via PATCH /broadcasts/:id without triggering a send.

curl -X POST https://api.eusend.dev/broadcasts/3fa85f64-5717-4562-b3fc-2c963f66afa6/send \
  -H "Authorization: Bearer eu_live_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "scheduled_at": "2026-06-01T09:00:00Z"
  }'

Send yourself a copy of the broadcast before it goes to the audience — the real message, through the real sending path, so you see exactly what a recipient sees.

Available on every plan, including Free. This is how you evaluate a broadcast without a paid subscription.

Recipients must be addresses on domains you have verified. A test send puts real mail on the wire without the plan gate, so it is restricted to inboxes you already control — pass an address anywhere else and you get 403 with code DOMAIN_NOT_VERIFIED.

What a test send does and does not do:

• Subject is prefixed with [Test], so a test copy is never mistaken for the campaign.
• Contact variables render with sample values ({{first_name}} becomes Alex), rather than collapsing to an empty string and hiding a greeting that will look wrong later. Custom properties are borrowed from a real contact in the audience, since only your data knows what {{plan}} should look like.
• The unsubscribe footer is included so you can see it, but its link is inert — there is no contact behind a test send to unsubscribe.
• It counts against your daily and monthly sending limits, because it is a real send.
• It does not change the broadcast's status, its recipient list, or its stats. Send as many tests as you like; the campaign stays a draft until you send it.

curl -X POST https://api.eusend.dev/broadcasts/3fa85f64-5717-4562-b3fc-2c963f66afa6/test \
  -H "Authorization: Bearer eu_live_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "to": ["you@yourdomain.com"]
  }'

Cancel a scheduled or in-flight broadcast. Emails already sent are not recalled.

The rest of the broadcast surface:

List broadcasts.

Get broadcast details.

Update draft / set scheduled_at.