POST
Publish the stored draft to the live storefront

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.

Headers

Idempotency-Key
string
required

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

application/json

The only input is the version you expect. A draft or a schema_version sent here is refused by name: this route promotes the document the server already holds, and accepting one in the body would put a tree that never passed validation in front of every shopper.

expected_updated_at
string
required

The updated_at you last read, and NOT nullable here: there is nothing to publish before the first draft save, so null would be a precondition that can never hold. A mismatch is 409 config_modified and means the draft moved under you.

Response

Success

data
object