Save a page draft (PATCH alias of POST)

Same behaviour, body and responses as POST /pages/{page_id}/draft. Drafts are always a full replace, so there is no merge difference between the verbs.

Authorization

AuthorizationBearer <token>

Personal access token tied to a user account. Requires the X-Nimbu-Site header to scope requests.

In: header

X-Nimbu-Site<token>

Identifier of the site context when authenticating with a personal access token.

In: header

Path Parameters

page_id*string

Existing page id, or a new ObjectId to create a draft-only page

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

title?string

Draftable page title.

seo_title?string

Draftable SEO title.

seo_description?string

Draftable SEO description.

seo_keywords?string

Draftable SEO keywords.

og_image?

Draftable Open Graph image (FileRef or File upload).

fixed_locale?string

Draftable fixed locale.

locales?array<string>

Draftable locale list.

items?

Same merge semantics and theme 422s as PageUpsert.items (hash keyed by editable slug), for both drafts of a live page and draft-only pages. Stored on the draft as a page_items snapshot; a raw page_items array is also accepted on draft-only pages and replaces the snapshot.

reserved_fullpath?string

Draft-only pages (POST /pages/{new_id}/draft when {id} is not an existing page): reserved public path.

fullpath?string

Alias of reserved_fullpath when creating a draft-only unpublished page.

parent_id?string

Draft-only: parent page id. Validated against reserved_fullpath segments.

position?integer

Draft-only: tree position.

template_id?string

Draft-only: template to render the unpublished page with.

[key: string]?any

Response Body

`application/json`

curl -X PATCH "https://example.com/pages/string/draft" \  -H "Content-Type: application/json" \  -d '{}'

{
  "id": "string",
  "page_id": "string",
  "future_page_id": "string",
  "reserved_fullpath": "string",
  "content": {},
  "updated_at": "2019-08-24T14:15:22Z"
}