List a marketing flow run's steps
A run’s append-only audit trail, OLDEST FIRST: this run executed this step, and this is what happened. It is the only list on this API that reads forwards, because it is a story in order. THIS IS WHAT MAKES A FLOW DEBUGGABLE. Without it, “the customer never got the email” and “we never sent it” are the same observation from outside. outcome=enqueued means the send was HANDED TO THE MESSAGE SPINE, not that it was delivered: the spine owns dedupe, the compliance gate, dispatch and retries, and can still refuse a send recorded here. message_id is set on a send step and is what you join against the notifications family to see the verdict.
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Path Parameters
Query Parameters
Rows per page. Out of range is a 400 rather than a silent clamp, so a client asking for more than 100 learns it did not get it.
1 <= x <= 100The next_cursor from the previous page. Opaque: decode nothing from it and construct nothing by hand, since its encoding is not part of this contract. Omit it to read the first page.
