Read a campaign’s current state, sequence, and prospect pipeline. The primary polling target after launching.
prospects_by_status — a simple count-by-status map, ideal for progress bars (sent: 34 / total: 120)prospects_by_node — a two-level nodeId → status → count map, useful for pipeline visualization (which step is holding up the cohort)launchCampaign. status and stats.sent are the fields that actually move — everything else is mostly static once the campaign is launched.
| Campaign state | Cadence |
|---|---|
launching | every 30 s until it flips to active (typically ≤ 2 min) |
active with stats.sent < stats.total | every 1–5 min |
paused | stop polling; wait for user action |
completed | stop polling |
status === "completed"stats.completed + stats.replied + stats.bounced + stats.timed_out >= stats.totalstatus === "paused" and the user hasn’t asked to resumeBearer authentication header of the form Bearer <token>, where <token> is your auth token.
Campaign UUID
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$Campaign detail with sequence and prospect aggregates.
Canonical campaign entity.
Map of prospect status → count, e.g. { "pending": 42, "sent": 34, "replied": 2 }. Use this for progress bars and pipeline summaries.
Two-level map: nodeId → status → count. The key __none__ holds prospects with no current node (not yet started or terminal).