resume_drip
Resume a drip you paused. It only works on a drip still in status paused that was NOT edited since, and the same checks the app runs apply first: the plan lets drips run and includes that channel, an SMS drip has a registered 10DLC number, the channel is not paused by Sweeppea, and no step is held by Sweeppea support. A refusal explains itself in the message, in plain prose — an edited drip answers 409 with "This drip was changed after it was paused. Resume it from Drip Marketing in the app, where the full checklist runs." (verified live), and a drip that is not paused answers 409 naming the status it is actually in, such as "This drip cannot be resumed: its status is active. Only a paused drip can be resumed." Read that message back to the user. The docs also describe a machine-readable code in api_data.Reason — Blocked, EditedSincePause or StepsNotActivated (409); PlanDoesNotAllowSharing, ChannelNotInPlan, NoRegisteredSmsSender or StaffHold (403); ChannelPaused (423) — but no refusal has yet been observed carrying it. The api_data envelope itself IS real — a pause refused on a draft returned api_data.Status (verified live 2026-10-13) — so what remains unobserved is Reason specifically, not the envelope that would hold it. No refusal of THIS tool has been read through this server at all. Use Reason when it is there and never claim a Reason the response did not include. PlanDoesNotAllowSharing means the plan does not include running drips at all — only Sweeppea support changes that. A 423 means Sweeppea itself paused sending on that channel: not something the account did, not something retrying fixes. A drip edited after pausing, or blocked by the platform, CANNOT be resumed here at all — it is resumed in the app, where the full launch checklist runs; say that instead of trying again. On success (verified live) the drip returns to status active with PausedAt back to null, contacts continue from the step they were waiting for and no step is sent twice, and the response carries note, the API own wording that the sequencer runs every 5 minutes. The drip picks up within those few minutes rather than instantly, so never report that a step already went out. The reverse is 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 |
|---|---|---|---|
| drip_token | Yes | The drip campaign token (UUID v4) of a paused drip that has not been edited since |