Create a broadcast
Creates an unscheduled broadcast draft for your project, optionally seeding the default first message and default content from message.content.body. At this time audience and schedule fields are rejected with 422.
Authorizations
Accepts either a raw API key or Bearer <key>.
Headers
Optional dated API revision for the request. Must use YYYY-MM-DD format.
^\d{4}-\d{2}-\d{2}$"2026-03-01"
Body
Create an unscheduled, unlaunched broadcast draft. Audience, segment,
trigger, schedule, send, launch, and lifecycle fields are not supported
and are rejected with 422 Validation error.
Broadcast name. Trimmed before validation; must be non-blank.
1 - 255Messaging channel. Defaults to email when omitted. Supply the
matching channel when the initial content is for sms or push.
email, sms, push Optional initial message. When present it initialises the server-provisioned default first message and default content.
Labels to apply to the new broadcast. Each label is stored lowercased, must be non-blank, must not contain a comma, and must be at most 255 characters once lowercased.
Response
Broadcast draft created.
A broadcast: a one-off or recurring message sent to an audience.
Broadcast name.
Delivery channel.
email, sms, push Scheduling details for the broadcast. type indicates whether the
broadcast is sent once or on a recurring schedule. Additional
scheduling fields (such as scheduled_at, cron,
next_scheduled_at, batches, and timezone_detection) may also be
present.
Broadcast status. archived is returned for archived broadcasts on the detail endpoint.
draft, scheduled, sending, sent, cancelled, active, paused, archived Labels applied to the broadcast. Always present; [] when the broadcast has none. Labels are stored lowercased.

