POST
Unpublish a blog post

Authorizations

Authorization
string
header
required

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

Idempotency-Key
string
required

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

postId
string
required

Body

application/json

Takes no parameters, and an empty body is expected. Returns the post to draft, removing it from the storefront and from the /blog-posts read family while keeping the body, the slug and every revision. It CLEARS published_at, unlike the page family's unpublish which keeps it, so republishing stamps a new one. This is what a migration wants instead of a delete, and it is why this family publishes NO delete: unpublish is reversible and a hard delete that 404s every inbound link is not.

Response

Success

data
object