Withdraw Contacts From Sequences
POST /contacts/withdraw-from-sequences
Take contacts OUT of a sequence. They stop receiving its steps.
remove_all=true withdraws them from EVERY sequence they are enrolled in
and ignores sequence_id - the wider blast radius of the two, and never
the default.
response is REQUIRED by the app handler rather than decoration: it sets
a status on it for the partial-withdrawal case, so omitting it is an
AttributeError on every call.
Authorizations
Parameters
Header Parameters
Request Body required
Take contacts OUT of a sequence. They stop receiving its steps.
remove_all=true withdraws them from EVERY sequence they are enrolled
in and ignores sequence_id; that is the wider blast radius of the two
and it is never the default.
Responses
200
Successful Response
object
An open envelope for one record, one dashboard or one job receipt.
Open because most of these reads are COMPUTED shapes - an engagement summary, a next-best-step, an intelligence status - that grow with the product, and dropping a field from an advisory read makes it say “nothing to report” rather than “we did not tell you”.
object
object
Whether there are more pages
Items per page
Current page number (1-indexed)
Total number of items
422
Validation Error