Skip to main content
POST
Pause Subscribers in a Sequence
Hold specific contacts on the step they are on, then continue them later with resume subscribers. Use this when a contact’s onboarding should stop for a while, for example while their account is blocked or under review, without cancelling the enrollment or restarting the sequence. A paused enrollment:
  • Gets no further steps from this sequence until you resume it.
  • Keeps its step, its entry event properties, and its stop-condition snapshots.
  • Still counts as enrolled, so the same contact cannot enter this sequence again while paused.
  • Is still ended by an unsubscribe, a bounce, or cancel enrollments.
  • Does not react to events until you resume it. If the contact is paused on a wait-for-event step and the event arrives meanwhile, the step continues as soon as you resume them.
The request applies immediately; there is no dry run. Pausing an enrollment that is already paused changes nothing and reports already_paused.
This pauses individual contacts. To stop new contacts from entering the whole sequence while everyone already in it continues, use pause enrollments instead.

Request

string
required
Sequence ID.
array
Subscriber IDs to pause. IDs that match no contact come back in notFound.subscriberIds.
array
Subscriber email addresses to pause, matched case-insensitively. Emails that match no contact come back in notFound.emails.
string
Note stored on each paused enrollment and returned as pauseReason by list enrollments.
Send subscriberIds, emails, or both. Up to 500 targets combined per request.

Outcomes

Every active, waiting, or paused enrollment the targeted contacts have in this sequence is returned in enrollments with one outcome: Contacts that exist but have no enrollment in this sequence are listed in notEnrolled. A contact can have more than one enrollment in a sequence that enrolls per matching field value; every one of them is paused.

Responses