Put contacts into a campaign
Starts a campaign for contacts you already have, which is how a list that came in before the campaign existed gets dialled.
Accepted contacts are queued; the rest are counted by why they were not. A contact on do-not-call is skipped, always, and no argument to this endpoint overrides that.
Answers 202. The work continues after the response, so the contacts enter the campaign shortly afterwards rather than before you get an answer.
Only on a sub-account with no CRM. A CRM-backed sub-account starts campaigns from its CRM, and enrolling here as well would give one contact two triggers and eventually two cadences.
Cookie-auth callers must send the x-csrf-token header.
Required API key scope: contacts:write.
Authorizations
Send your API key as Authorization: Bearer YOUR_API_KEY.
Query Parameters
The sub-account. It is the only thing that identifies the tenant on these routes, and it is re-checked against your access on every call. A sub-account that keeps its contacts in a CRM answers 400.
Body
The campaign, and who to put in it.
