Update 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
An omitted field is left unchanged; a nullable field sent as NULL is CLEARED, which is the only way to remove a stale SEO title that is still being served. slug and title are NOT NULL columns and reading_time_minutes is set-only, so null on any of the three is a 400 rather than a silent skip; send [] to remove every tag. A patch naming nothing is refused, so a client with a misspelled field does not read a green light for a no-op. PATCH rather than PUT: status, published_at, scheduled_publish_at and the post's revisions are all state this body cannot express, so a whole-resource replacement reading would be a lie. Every value is an absolute target, so replaying converges. A patch to a PUBLISHED post is live immediately; there is no draft copy of a live post.
Response
Success
