List marketing flow runs
One row per contact per journey: who is in a program, which step they are on, and when they next move. ?flow_id= answers “who is in this program” and ?contact_id= answers “which programs is this person in”. The second is the reconciliation an integration actually performs on a customer record, and no per-flow route could answer it without walking every flow in the store, which is why runs are a top-level collection here rather than nested under a flow. ?status= takes active, waiting, completed, exited, errored or cancelled. waiting is the durable-timer state a long program spends most of its life in; next_run_at says when it moves, and is a floor rather than an appointment. THE SCHEDULER’S OWN BOOKKEEPING IS NOT PUBLISHED. A run carries no lease, no attempt count and no trigger event id: the first two are this platform’s crash-retry internals and the third belongs to the events family.
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.
Query Parameters
Narrow to one program: who is in it and where they are. An id that names no flow in this store returns an empty page rather than a 404, because this is one optional filter among three and a caller reconciling by contact_id has no flow to verify.
Narrow to one person: which programs they are in across the whole store. This is the reconciliation a customer-record integration performs, and it is why runs are a top-level collection rather than nested under a flow.
Narrow to one run state. There is no claimed value here even though the engine has one internally: a leased run publishes as active, so accepting claimed would return rows whose published status is a different word from the one asked for. An unrecognised value is a 400.
active, waiting, completed, exited, errored, cancelled 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.
