Retrieve a blog category
One blog category, keyed on the IMMUTABLE id rather than the slug. The patch route rewrites slugs freely, so a slug-addressed route would publish an identifier that stops resolving the moment a merchant renames a category. THE SAME SHAPE THE LIST SERVES, and the same shape both writes answer with, so a row taken off a page can be re-read on its own. A 404 IS DELIBERATELY GENERIC and covers three conditions at once: no such id, an id belonging to another store, and a malformed id. Separating them would make this route an existence oracle over another merchant’s category ids.
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
