List a marketing flow's versions
A flow’s published step graphs, newest first. Each is frozen: publishing an edit appends a new version rather than rewriting an old one, and this platform holds no permission to update the row. THAT IS WHY THIS COLLECTION MATTERS. A contact three days into a five-day program keeps walking the version they enrolled on, so a run’s flow_version_id and the flow’s live_version_id routinely disagree, and only this route lets you see what each of them is actually running. The definition is returned in the SAME shape a publish accepts, so a client can read a version, change one step and post the result back without a second mapping.
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.
