Archive a blog post
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.
Headers
A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.
Path Parameters
Body
Takes no parameters, and an empty body is expected. Retires a post: it drops out of the storefront and out of the /blog-posts read family, and nothing is destroyed. THE DIFFERENCE FROM UNPUBLISH is published_at. Archive KEEPS it, so the date the post first went live survives as history; unpublish clears it and republishing stamps a new one. Use archive for a post that had a life and is retired, unpublish for one going back to draft. IT IS NOT A DELETE. This family publishes none, because the underlying delete is a hard DELETE that takes the body, the slug and every revision and 404s every inbound link. Archive is reversible by POST /blog-posts/{postId}/publish. It exists because status already publishes "archived" on every read, so until this route landed a client could observe a state no call could produce. Absolute, so a replay converges: archiving an archived post leaves it archived with published_at untouched.
Response
Success
