Drafts and publishing

Publish a scheduled version immediately

Publishes an already scheduled page or theme version now instead of waiting for publishAt. This is the same operation as "Publish now" in Studio's scheduled content manager. To publish an unscheduled page draft, use POST /publish-versions/{versionId} instead.

Outcomes

  • 200: version is the published row (status: "PUBLISHED", outcome: "published"). For a page, pageUpdatedAt and projectUpdatedAt give the new live revisions.
  • 200 with cacheDelivery: "degraded" and a warning: content is live but cache invalidation failed. The row keeps its publishAt retry marker and edge delivery is retried without replaying content. Do not publish again.
  • 409 CONFLICT: the version could not be published, for example because live content moved since it was scheduled (it is cancelled; a draft returns to ACTIVE), or because it is not scheduled (a theme version, a page version that is neither a draft nor scheduled, or a draft that did not transition). Nothing was applied; details carries the stored row when there is one, so you can reconcile.
  • 409 STALE_PAGE: the draft head or its live base moved. Re-read and retry.

Required scope: content:publish

post/versions/{versionId}/publish-now

Request

  • Base URL
    https://studio.weaverse.io/api/v1/content
  • Auth
    HTTP bearer

Request body

projectIdstring required
type'page' | 'theme' required

Response

Published (cacheDelivery=degraded if edge delivery pending)

object required

Changes

No recorded changes to this operation across all 1 revision of this API.