remove_drip_contact
Take ONE contact out of a drip campaign so it receives no further steps of that sequence. confirm=true is REQUIRED. This is PERMANENT, and the API documents it as such: one enrolment per address per drip, ever — a contact removed here is NEVER enrolled again by this drip, not even if they enter the sweepstakes again. Tell the user that before they approve it. Messages already sent stay in the report. It takes someone out of this one drip and does NOT unsubscribe them: to stop every message to an address, use add_suppressions instead. The action is recorded in the account log. To stop the whole sequence for everyone instead, use pause_drip. Account-gated, and the two sides of this category are gated differently: this write needs BOTH the Drip Marketing module AND the Send Message module — two separate 403 messages, and either one missing fails the call — while the reads need only Drip Marketing. The gate was NOT observed on the test account, so on a 403 read back which module the API named instead of guessing. Drips are created, edited, activated and deleted ONLY in the Sweeppea app: those actions run a launch checklist (template, sender, 10DLC registration, content screening, plan allowance) that this API deliberately does not reproduce. There is no create endpoint and that is by design, not a gap — the API leaves these writes out on purpose (confirmed by the API maintainer, October 2026) — say so plainly instead of hunting for a workaround, and never propose or invent a tool for it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | Yes | Must be true. Set it ONLY after the user explicitly approved THIS action in this conversation, having been told what it does and that it cannot be taken back: this contact stops receiving every remaining step of this drip and can NEVER be re-enrolled in it — the API allows one enrolment per address per drip, ever. Never assume, never carry an approval over from a previous item, never set it to satisfy the schema. | |
| drip_token | Yes | The drip campaign token (UUID v4) | |
| source_token | Yes | The contact: a ParticipantToken, OR a lead / subscriber id. NOT always a UUID — pass it through exactly as you received it, and read SourceType in fetch_drip_enrollments to know which kind it is. Never feed it to get_participant without checking SourceType first. |