Get the rich document
Returns the Tiptap JSON doc, converting legacy blocks on first read.
View as MarkdownAuthorization
bearer In: header
Path Parameters
uuidResponse Body
application/json
curl -X GET "https://example.com/v1/pages/497f6eca-6276-4993-bfeb-53cbbbba6f08/doc"{ "doc": {}, "rev": 0, "updated": "2019-08-24T14:15:22Z", "lastEditedBy": "c8f46d5a-a913-440d-93ff-c5119da72e7a"}Delete a trashed page permanently
Only a page that is already in the trash (archived) can be deleted forever; a live page returns 409. The page goes with its trashed sub-pages. A sub-page that is still live is kept and moved up to the deleted page's parent (or the space root if that parent is trashed).
Save the rich document (optimistic concurrency)
Saves the doc with the revision the client loaded. A rev mismatch returns 409 with the current server doc so the editor can merge instead of clobbering another writer. Optionally syncs outgoing wiki-link edges in the same save. A tool publishing from an outside source also sends publishedRev, the rev its last publish wrote (easerix#461). If the page has moved past it, people edited it in Notes since, and the save is refused with 409 code edited_since_publish unless force is true. A save that carries publishedRev or force is recorded as a publish (publishedRev/publishedAt on the page). Ordinary saves omit both and are unaffected.