Menu

Preview a contact's journey step path without sending

POST/v1/journeys/{id}/simulate

Requires an API key with the journeys:read scope. About keys and scopes

Previews a run without sending. entry says whether the contact would enter now: a date journey needs a valid date in its field; an event journey checks the supplied eventProperties against the entry conditions, then reentry. The path follows branches on eventProperties and filters and splits on the contact as they are now; a wait-until step takes its match path. Each send step is checked against suppression, consent, topics and devices: would_send, unreachable (takes the fallback path) or would_skip, with the refusal code in reason (DRAFT_INCOMPLETE for a send step not yet finished: a draft simulates too). Message limits and send-time scheduling are not previewed.

Path parameters

idstringrequired

uuid

Request body

contactIdstringrequired

The contact to simulate.

uuid

eventPropertiesobjectoptional

Properties of a trigger event to simulate, checked against entry conditions.

default {}

Returns

Returns 200 OK. Otherwise returns an error; Errors lists every code and which to retry.

contactIdstringrequired

uuid

entryobjectrequired

Whether the contact would enter the journey now.

2 child attributes
eligiblebooleanrequired

Whether the contact would enter now.

reasonstring | nullrequired

Why not: no_date, entry_conditions_not_met, already_enrolled or in_cooldown.

pathobject[]required

The steps the contact would pass through, in order.

4 child attributes
stepIndexintegerrequired

Index of the step in steps.

min -9007199254740991 · max 9007199254740991

typestringrequired

The step type.

outcomestringrequired

What the step would do.

reasonstringoptional

Why a send step would not send: the send guard's error code.