Update a broadcast
Updates broadcast metadata (name and a constrained channel). audience and schedule fields
are rejected with 422. A channel change is accepted only while the broadcast is a single-message
draft whose current message is not yet sendable: switching channels will reset the
message content body. This endpoint cannot be used to update broadcast content. See dedicated endpoints.
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"
Path Parameters
Broadcast ID.
Body
Update message/content-adjacent broadcast metadata only. channel may
change only while the broadcast is a single-message draft whose current
message is not yet sendable; that switch resets the message content body.
Audience, segment, trigger, schedule, send, launch, lifecycle, and run
fields are rejected with 422 Validation error.
Response
Broadcast updated.
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 
