Retrieve a seo
One resource’s stored override, in the merchant’s own words. NEVER THE LOCALISED TEXT the storefront renders, which is what makes this the correct read half of a read-modify-write against the PUT: what comes back here is exactly what a replayed PUT would write. Translated meta titles are read and written through /api/v1/translations. A resource with no override is 404, not a 200 carrying blanks. The two states are different and only one is reachable by a write: an override whose every field is blank EXISTS and suppresses nothing, while no override at all leaves the resource on its catalogue text.
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
