Skip to main content
GET
Simulate Sequence

Simulate Sequence

Dry-run a sequence. Nothing is sent, no one is enrolled, and tags, lists, and discounts are not written. Activating a sequence does not enroll anyone automatically. Without a subscriber this reports who currently matches and whether the sequence is ready (existing list, tag, and segment matches can still be enrolled by hand). Pass subscriberId or email to also walk that stored contact through the graph and see which branch they take. Use that to check cases like “would a paid user get the upgrade email?” Call this before Enable Sequence.
sendsMail is always false. To send one saved email step to a reviewer, use Send Sequence Step Test.
This endpoint always requires both sequences:read and subscribers:read because aggregate results include contact samples, even when no subscriber is selected for a path preview.

Request

string
required
Sequence ID.
string
Optional stored subscriber to walk through the graph. Do not pass with email.
string
Optional stored subscriber email to walk through the graph. Do not pass with subscriberId.
integer
How many currently matching contacts to include in the sample. Defaults to 10, maximum 25.

Response fields

boolean
Always false.
string
Plain-language description of who enrolls after activation.
boolean
Whether an exact current-match count is available. This is false for frequency and inactivity triggers, whose matches are evaluated by the hourly worker.
number
Always 0. Activating a sequence does not enroll anyone.
number | null
Contacts who match the trigger right now and are not already in the sequence. These people are not auto-enrolled. null when currentlyMatchingAvailable is false.
boolean
false when activation blockers are present (missing trigger, unattached email, disconnected discount provider, and similar).
object
Walked graph for the optional stored subscriber, or null when none was passed. Each step may include an outcome with verdict (passed, failed, or unknown) and assumed when the branch could not be known statically.
number
Email and A/B-test steps traversed by the selected path, whether or not the subscriber can currently receive them.
number
Traversed email steps deliverable for the subscriber’s current email and subscription status. Transactional steps remain deliverable to unsubscribed contacts; bounced and email-less contacts have no deliverable emails.

Responses