Replace a page
Replaces the whole document: every field left out is reset to its default. PATCH changes only the fields sent. Completely replace a page document.
Use cases:
- Complete page updates
- Moving pages in the tree structure
- Replacing page content entirely
Requires _targetId and _position for page tree positioning.
Access: an API key with content:pages:write (or a master above it: content:pages:all, content:all, admin:all). In published mode (the default) it goes live too, so the key also needs content:pages:publish (or a master above it); send aposMode=draft (or a draft _id and no aposMode) to change only the draft. A signed-in person may call it as far as their own permissions allow; anyone else gets 403.
Rate limit: the key’s own writes-per-minute limit, set when the key is created (default 120); over it, 429 with Retry-After.
Authorizations
Path Parameters
Query Parameters
Body
The whole page: every field left out is reset to its default (PATCH changes only the fields sent).
The ribbon of phrases scrolling across the top of the footer. Its phrases and the site-wide default are set in Site design → Footer: Marquee.
inherit, on, off, null Response
Page replaced successfully
A page: the fields every page has, and each page type’s own (type says which page type it is; a field belongs only to the page types that define it).
The draft’s preview share key, while its share link is on: the link is the draft’s _url with aposShareKey and aposShareId (the draft’s _id) in its query. Absent otherwise, and on published documents.
"k3v9x2m7q1z8w4p6"
The ribbon of phrases scrolling across the top of the footer. Its phrases and the site-wide default are set in Site design → Footer: Marquee.
inherit, on, off, null