Campaigns
Send a template to a segment — now or on a schedule — with server-enforced safety gates.
A campaign is a one-to-many send: a template (content) + a segment (audience) + a from-address on a verified domain, sent immediately or scheduled. Campaigns are the end of the contacts → segments → campaigns pipeline.
A campaign, not a loop of single sends
A newsletter or an announcement is a campaign, whether you start it here, from the API (POST /api/v1/email/campaigns, then /email/campaigns/{id}/send), the MCP server or the CLI. One request covers the whole audience: we pace the sends, retry temporary failures, add the unsubscribe link and header, and report opens, clicks and bounces together.
You don't have to import contacts first. From the API, a campaign takes up to 5,000 addresses inline as recipients in place of a segment_id: we make a segment from them, and addresses we haven't seen become subscribed contacts, so an unsubscribe is remembered for the next send. A larger list goes in as several campaigns, or as a contact import and a segment.
One API call per recipient runs into the request limit
The API takes 10 requests a second per workspace by default. A script that sends a list as single emails faster than that gets 429 for the rest, and a 429 means that recipient got nothing: nothing queues a refused request for you. If each recipient needs different content, send batches of up to 100, which count as one request each. Rate limits has the details.
Send-readiness gates
Before a campaign sends, every one of these must hold (enforced on the server):
- The from-domain is verified and sending-allowed (re-checked at send, not just at create).
- There's a non-empty subject (from the campaign or the template default).
- The template is a publishable marketing template — not transactional, not an archived/draft template.
- The segment is not archived and has at least one subscribed member.
- Any schedule is within bounds — not in the past, and no further than 90 days out.
When a send is blocked, the validation dialog lists exactly which gate failed and how to fix it. The API returns the same reasons as a structured 409/422.
The validation dialog also shows who will receive the campaign. Its numbers (Members, Sendable, Suppressed, Excluded, and Missing data when some contacts lack a template variable) filter a read-only list of the segment's contacts, with each one's status and the reason in plain words: unsubscribed, on the suppression list (bounced, for example), opted out of the campaign's topic, excluded from this campaign, or missing a value. Seeing the list needs permission to view contacts; without it the dialog shows the counts only.
Lifecycle & archiving
A campaign moves through draft → scheduled → sending → sent (or canceled/failed). Terminal campaigns can be archived directly; a non-terminal campaign must be canceled first. Archived campaigns are restorable and auto-pruned after ~30 days.
Scheduling semantics
A schedule in the past is treated as "send now"; a schedule beyond 90 days is rejected at both create and send time. These bounds are consistent across the dashboard and the v1 API.
Edit, unschedule or copy a campaign
A draft can be edited from its page or with PATCH /api/v1/email/campaigns/{id}: name, subject, from, preview text, template, segment, topic, tracking, variable fallbacks, exclusions and the saved send time. Changed values get the same checks as create. A value equal to the draft's is no edit, so an integration can send back the object it read.
A scheduled campaign is locked. To change it, unschedule it (the Unschedule button, or POST /api/v1/email/campaigns/{id}/unschedule): it goes back to a draft and its send time is cleared, so the next Send needs a time or null for now. A campaign that has started sending can't be unscheduled; cancel it instead.
Duplicate (POST /api/v1/email/campaigns/{id}/duplicate) copies a campaign's setup into a new draft, never its send time or results. Pass an Idempotency-Key so a retry returns the same copy. The SMS campaign routes work the same way, and the MCP server, SDKs and CLI have the same operations.
A copy mails the whole segment again
Duplicating a canceled or sent campaign and sending the copy reaches everyone in the segment, including people who already got the original. Add them to the copy's excluded_contact_ids first if they shouldn't get it twice.