30-day schedule limit
The publish time is at most 30 days from when you save (it used to be almost a year). Further out returns 400invalid_scheduled_at. Posts queued earlier still publish on time; only creating or editing is checked. Agents that need a later date should set it again when it is within 30 days.Editing on the web, the updated_by field
Users can edit the content or time of unpublished posts up to 2 minutes before publish time. Posts now return updated_by ({ kind, id, at }). Agents should re-read GET /posts/:id before relying on scheduled_at or content of a pending post.Validation errors list every reason
A 400 from post validation now haserror.issues[], each item { code, message }. error.code is still the first reason.Media URLs created by the web
/api/media/... URLs created by uploading on the web can be used like any media URL when publishing through the API.404 classified by HTTP status
A well-formed id that does not exist returns<entity>_not_found (for example post_not_found). Clients should branch on HTTP 404, not compare code with NotFoundException.
