Retrieve a store policy
One policy, in the same shape the list serves. The path segment IS the policy_type: privacy, terms, refund, shipping or cookie. KEYED ON THE TYPE, NOT ON AN ID, and no id is published. policy_type is half the row’s unique key so it never changes, which makes it safe to persist as your own reference. A type outside the five is 400 invalid_policy_type, because you mistyped a constant. A valid type the merchant has not written is 404, including one that exists only in another store, so this route cannot be used to probe for a policy you were not granted. An UNPUBLISHED policy answers 200 with status draft here rather than 404. Branch on status before showing it to anyone.
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
