Create a content 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.
Headers
A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.
Body
EVERY page created here lands as a DRAFT, and status is not settable: publishing puts content in front of every shopper immediately, with no review step, so it is a second deliberate act at POST /pages/{pageId}/publish. A body carrying "status" is refused rather than ignored, because a 201 that quietly dropped it would leave the client believing a page is live that no shopper can reach. The slug must be unique in the store; a taken slug is 409.
Response
Created
