List geo rules
The store’s geolocation rules: which shoppers are routed where, and how. ONE LIST COVERS BOTH QUESTIONS a client asks. ?enabled=true is the set the storefront actually evaluates; ?enabled=false is what the merchant has staged and not switched on; omitting it returns both. PAGED BY CREATION TIME, NOT BY priority. priority is the evaluation order and it reads first in the dashboard, but it is an editable, non-unique integer, so a cursor over it would drop or repeat rules the moment a merchant re-prioritised one mid-walk. Sort on priority yourself once you hold the page.
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
true narrows the page to the rules the storefront evaluates, false to the rules the merchant has staged and not switched on. Omit it for both. A value that is not a boolean is a 400 rather than an ignored filter.
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.
