Publish a storefront template's draft to shoppers
Makes the STORED draft the markup every shopper renders for this page kind. It publishes what the server already holds, never markup in this request: save it with PUT /api/v1/storefront-templates/ first, then publish the updated_at that write returned. Sending markup here is a 400. THE PRECONDITION MATTERS MORE HERE THAN ON THE WRITE. A stale draft save loses one edit; a stale publish makes markup you never saw the page every shopper gets, and answers 200 as though it were yours. null is not accepted: it would assert the template does not exist, and there is nothing to publish when that is true. AN EMPTY DRAFT IS REFUSED with 409 nothing_to_publish. Promoting it would take the page off the storefront rather than update it, and this API offers no route that does that. RETRIES: replaying the same Idempotency-Key returns the recorded response and publishes nothing. A FRESH key after a publish that already succeeded is 409 template_modified, because that publish moved updated_at.
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.
Path Parameters
Body
The only input is the version you expect. draft_markup sent here is refused by name: this route promotes the document the server already validated, and accepting one in the body would put markup that never passed the gate in front of every shopper.
The updated_at you last read, and NOT nullable here: null asserts the template does not exist, and there is nothing to publish when that is true. A mismatch is 409 template_modified and means the draft moved under you, so what you would have published is somebody else's markup.
Response
Success
