Sequences
Resume paused subscribers in a sequence
Changed onContinues paused contacts from the step they were paused on, with the status they had. Nothing restarts or is skipped. Waits keep their original wall-clock time, like a whole-sequence pause - a wait that ran out while paused continues right away, and one that has not still ends when it would have. Enrollments of the targeted contacts that are not paused are reported with outcome not_paused and left alone. When the sequence itself is disabled, sequenceRunning is false and the resumed contacts continue once it is enabled.
post/sequences/{sequenceId}/enrollments/resume
Request
- Base URLhttps://api.sequenzy.com/api/v1
- URLhttps://api.sequenzy.com/api/v1/sequences/{sequenceId}/enrollments/resume
- AuthHTTP bearer
Path parameters
sequenceIdstring required
Sequence ID
Request body
Example request
{
"subscriberIds": [
"sub_abc123"
],
"emails": [
"ada@example.com"
]
}Response
Request applied; each targeted enrollment reports its outcome
Example response
{
"success": true,
"sequenceId": "seq_abc123",
"enrollments": [
{
"enrollmentId": "tok_abc123",
"subscriberId": "sub_abc123",
"subscriberEmail": "ada@example.com",
"currentNodeId": "node_delay_2",
"status": "paused",
"pausedAt": "2026-03-02T09:00:00.000Z",
"outcome": "paused"
}
],
"notEnrolled": [
{
"subscriberId": "sub_def456",
"email": "grace@example.com"
}
],
"message": "Paused 1 enrollment.",
"resumedCount": 1,
"sequenceRunning": true,
"enqueuedCount": 1
}Changes
- info
endpoint added
- info