Remove many contacts from the sequence
SEQ-26: scope=‘all’ resolves the target set SERVER-SIDE from the given status/search filters — never from a client-side id list — so the action covers every matching enrolment across pages. Each removal keeps the durable single-remove semantics.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
SEQ-26: one bulk removal.
scope='all' resolves the target set server-side from the filters
below; scope='ids' uses the explicit list.
1000SEQ-49: with scope='all', act on only the FIRST n of the resolved set (in the roster's order) instead of every match.
1 <= x <= 100000ids, all 255Where one contact stands in one sequence.
ACTIVE rows carry a due_at and are what the tick claims; CLAIMED is the
in-flight guard between claim and outcome. PAUSED (SEQ-30) is a deliberate
per-contact hold: unclaimable because the tick claims strictly on ACTIVE,
yet still LIVE — it keeps its step and its one-live-sequence slot, and a
compliance stop (reply, unsubscribe) reaches it. Everything else is
settled: COMPLETED walked off the end; STOPPED was halted (reply,
unsubscribe, bounce, manual, company pause); FAILED is terminal per the
phase-1 ruling; SUPPRESSED was on the do-not-contact list;
SKIPPED_DUPLICATE lost the one-live-sequence-per-contact rule, with the
reason visible in the grid.
active, claimed, paused, completed, stopped, failed, suppressed, skipped_duplicate reply, unsubscribe, bounce, manual, company_reply, row_left_audience, step_removed, removed Response
Successful Response