GET
List marketing flows

Authorizations

Authorization
string
header
required

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

status
enum<string>

Narrow to one lifecycle state. live is the set that is actually enrolling and mailing people right now, which is the question worth asking first. An unrecognised value is a 400 rather than an empty page: "no flows are live" and "you spelled live wrong" would otherwise be the same answer.

Available options:
draft,
live,
paused,
archived
trigger_type
enum<string>

Narrow to one kind of trigger. An unrecognised value is a 400, for the same reason.

Available options:
event,
segment_entry,
manual
updated_after
string<date-time>

Flows touched at or after this RFC3339 instant. live_version_id IS THE FIELD THAT MOVES, and it decides which version of an automation actually runs against shoppers: publishing a new version rewrites the parent without creating one, so a cached flow leaves you believing an older version is live. Supplying it CHANGES THE ORDER of this endpoint: the default walk descends created_at, and this one climbs updated_at, which is the only ordering in which a keyset walk over a mutable column cannot skip a row. A flow edited mid-walk moves forward past your position and is returned again, so the walk is AT LEAST ONCE. The bound is INCLUSIVE, so resuming from the newest updated_at you hold re-delivers the rows sharing that instant. A cursor belongs to ONE ordering and is refused by the other.

limit
integer
default:20

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.

Required range: 1 <= x <= 100
after
string

The 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.

Response

Success

data
object[]
page
object