GET
List pages

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>

Filter by publication state. Omit it to receive both. An unrecognised value is a 400 rather than an empty page: a client filtering on "live" would otherwise conclude the store has no published pages.

Available options:
draft,
published

Case-insensitive substring match on slug and title. SQL wildcards in the term are escaped, so a literal % or _ matches itself.

updated_after
string<date-time>

Pages touched at or after this RFC3339 instant, for reconciling incrementally instead of re-reading every page. That saving is larger here than on other lists, because this list carries the page BODY: without it a client re-reads the store's entire content on every sync. Supplying it CHANGES THE ORDER of this endpoint: the default walk descends created_at, and this one climbs updated_at. The direction is the whole point. Descending updated_at is unusable, because an edited page teleports to the head of the list and a paging client sees it twice while missing whatever it displaced; ascending, that same edit moves the row forward past your position and is simply handed to you again. So the walk is AT LEAST ONCE: apply the state of each row you receive and a repeat costs nothing, while a miss means serving stale body content you have no way to discover is stale. The bound is INCLUSIVE, so resuming from the newest updated_at you hold re-delivers the rows sharing that instant rather than dropping the ones your last page did not reach. A cursor belongs to ONE ordering and is refused by the other. DRAFTS ARE INCLUDED here exactly as in the default list, because this read feeds the merchant's own migration and review tooling.

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