Versions and errors

Version-bound writes

PATCH /api/v1/posts/{postId}, restore, and publish operations use the current tip version to prevent lost updates. Scheduling instead pins an existing versionNumber and a future publishAt UTC epoch second; it can publish that version after newer edits. Site, theme, and signup form changes use expectedUpdatedAt.

{
  "expectedVersionNumber": 3,
  "title": "Revised title"
}

When another write has created version 4, a request expecting version 3 returns HTTP 409 with CONFLICT.

Error model

REST errors are machine-readable and use the HTTP status that matches the failure:

Do not retry validation, authorization, or conflict failures unchanged. Network failures and rate limits may be retried only while the original user request remains active.