List Sequence Steps
GET /sequences/{sequence_id}/steps
List a sequence’s steps with their resolved copy. Read-only, no enrollment.
The step list from /preview without the sequence and channel envelope. Each
step carries the same rendered block described on /preview, so this is
the direct way to check what a given step will actually send.
Authorizations
Parameters
Path Parameters
Sequence ID
Sequence ID
Header Parameters
Responses
200
Successful Response
object
Response for GET /sequences/{id}/steps.
This route exists because callers reach for it first and used to get a bare
404, which sent them to /preview and its unrendered copy instead.
object
object
What a step’s copy actually looks like once spintax is resolved.
Exists because step_data is the stored TEMPLATE, not the delivered email.
A caller reading raw {{a|b|c}} back out of a field called “preview” has no
way to tell working spintax from broken spintax, which is precisely how a
working feature got reported as broken (see the PR that added this).
object
Body with spintax resolved to one variant
Findings from the same content-syntax validator that blocks launch, so a caller sees them here instead of discovering them as a 400 on run (or worse, as missing text in a delivered email). Each entry carries code, severity, message, field and snippet. An error-severity entry will block POST /sequences/{id}/run.
object
Count of top-level spintax blocks across subject + body. 0 means this step contains no spintax at all, which distinguishes ‘nothing to vary’ from ‘spintax failed to resolve’.
Subject with spintax resolved to one variant
Distinct emails this step can produce. Always >= 1; a value of exactly 1 means the copy is too templated to vary, which is a legitimate outcome and not an error.
False for this endpoint. Spintax is resolved but {{variables}} are left visible on purpose, because a preview has no contact and resolving against an empty contact would delete the token and show a hole in the copy. Variables fill in at send time.
Up to 3 distinct body renderings under different selection seeds. This is the proof that spintax works: if these differ, per-contact variation is functioning. Fewer than 3 entries means the copy cannot produce more.
True when the rendered copy above is what a recipient actually gets. False means content_issues contains errors that make the delivered email differ from this preview, because malformed tokens are silently DELETED at send rather than raising. Do not launch on a false.
422
Validation Error