Retrieve online store
The storefront builder configuration: the working draft, the published copy the storefront actually renders, and the version every write has to echo. ONE DOCUMENT PER STORE. There is no id and no list; the store comes from your key. A store that has never opened the builder answers 200 with an empty draft, a null published and a NULL updated_at rather than 404, and that null is what a first write sends as expected_updated_at. draft and published are OPAQUE JSON DOCUMENTS owned by the builder rather than by this API. Their internal shape is deliberately left undescribed here and changes with builder releases: read one, change what you mean to change, and send the whole thing back. published and published_at are NULL until the first publish, which is a different fact from an empty published document. Empty would mean the live storefront renders nothing.
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.
Response
Success
