Retrieve geo settings
The store’s geo configuration. A SINGLETON: one row per tenant, so there is no page block and no id in the path. A store that has never configured geo has no row, and this answers with the documented defaults (disabled, banner, hreflang on, 30 days) rather than a 404. “Geolocation is off” is the true answer to the question, and a 404 would make you branch on a missing resource to read a boolean you already know.
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
