List marketing forms
The store’s signup forms and pop-ups: where each renders, what it asks, and the consent block it shows. ?status=active is the set the storefront is actually serving right now. honeypot_key IS NOT PUBLISHED on any route in this family. It is the hidden field a real shopper never fills and a bot must leave empty, so it is the whole of the spam defence; a client that could read it could submit past it on every form in the store.
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
Filter by lifecycle state. Omit it to receive all three. ONLY active forms are served to shoppers, so ?status=active is how you ask what the storefront is showing right now, and it is the v1 replacement for the storefront's own form feed. An unrecognised value is a 400 rather than an empty page: a client filtering on "live" would otherwise conclude the store runs no signup forms at all.
draft, active, paused 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.
