Skip to main content
POST
Create broadcast

Authorizations

Authorization
string
header
required

API key authentication. Use your API key as the bearer token.

Body

application/json
name
string
required
Minimum string length: 1
Example:

"Newsletter - January 2024"

subject
string
required
Minimum string length: 1
Example:

"Your monthly update"

template_id
string<uuid>
required

Template ID to use for the broadcast email content. Required.

Example:

"123e4567-e89b-12d3-a456-426614174000"

from_email
string<email>

Sender email address. Required unless inbox_id or inbox_ids is provided.

from_name
string

Display name for the sender. Combined with from_email as 'Name ' when sending.

Example:

"Acme Newsletter"

reply_to
string<email>

Reply-To email address for broadcast emails.

preview_text
string

Preview text (preheader) shown in email clients.

Maximum string length: 500
Example:

"Check out our latest updates..."

segment_id
string<uuid>
topic_id
string<uuid>

Optional topic ID to categorize the broadcast for unsubscription management

Example:

"123e4567-e89b-12d3-a456-426614174000"

scheduled_at
string<date-time>
inbox_id
string<uuid>

Optional inbox ID. When provided, the inbox's name, from address, and reply-to address are used as defaults unless explicit values are given. Mutually exclusive with inbox_ids.

Example:

"123e4567-e89b-12d3-a456-426614174000"

inbox_ids
string<uuid>[]

Optional array of inbox IDs for inbox rotation. When set, emails are round-robin distributed across these inboxes, each using its own sender identity. Mutually exclusive with inbox_id.

Example:
sending_speed
enum<string>

Controls how fast emails are sent. 'auto' scales with recipient count (recommended), 'warmup' ~100/day, 'very_slow' ~100/hr, 'slow' ~1000/hr, 'normal' ~2000/hr, 'instant' sends as fast as possible.

Available options:
auto,
warmup,
very_slow,
slow,
normal,
instant
Example:

"auto"

tags
string[]

Tags for categorization. Lowercase, max 50 chars each, max 20 tags.

Example:

Response

Broadcast created

id
string<uuid>
required
Example:

"123e4567-e89b-12d3-a456-426614174000"

organization_id
string<uuid>
required
name
string
required
subject
string
required
from_email
string<email>
required
from_name
string | null
required
reply_to
string | null
required
preview_text
string | null
required
template_id
string<uuid> | null
required
segment_id
string<uuid> | null
required
topic_id
string<uuid> | null
required

Topic ID for categorizing the broadcast

Example:

"123e4567-e89b-12d3-a456-426614174000"

inbox_id
string<uuid> | null
required

Associated inbox ID for sender identity defaults

Example:

"123e4567-e89b-12d3-a456-426614174000"

inbox_ids
string[] | null
required

Inbox IDs used for inbox rotation

sending_speed
string | null
required

Sending speed setting for the broadcast

Example:

"auto"

status
string
required
Example:

"draft"

total_recipients
number | null
required
sent_count
number | null
required
delivered_count
number | null
required
opened_count
number | null
required
clicked_count
number | null
required
bounced_count
number | null
required
scheduled_at
string<date-time> | null
required
started_at
string<date-time> | null
required
completed_at
string<date-time> | null
required
tags
string[]
required

Tags for categorization.

Example:
sequence_mode
enum<string>
required

Whether follow-ups are sent as threaded replies (sales) or fresh standalone emails (marketing).

Available options:
sales,
marketing
Example:

"sales"

created_by
string<uuid> | null
required
created_at
string<date-time>
required
sequence_exit_conditions
object | null

Configurable exit rules evaluated by the sequence dispatcher before each follow-up. Supported keys: exit_if_in_segment_ids (string[]), exit_if_not_in_segment_ids (string[]).