Retrieve an online store revision
One revision WITH the configuration it captured, under “config”. This is the non-destructive half of a rollback: read a past design and compare it against the live one without restoring it over whatever is in the draft. The snapshot is served as it was captured, including its own schema_version, which may be older than the store’s current one. A revision belonging to another store is 404, not 403.
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.
Path Parameters
Response
Success
