Children returns a map of the direct children of a piece of content. A piece of content has different types of child content, depending on its type. These are the default parent-child content type relationships:
page: child content is page, comment, attachment
blogpost: child content is comment, attachment
attachment: child content is comment
comment: child content is attachment
The map will always include all child content types that are valid for the content. However, if the content has no instances of a child content type, the map will contain an empty array for that child content type.
ChildrenByType returns all children of a given type, for a piece of content. A piece of content has different types of child content, depending on its type:
Returns a map of the descendants of a piece of content. This is similar to Get content children, except that this method returns child pages at all levels, rather than just the direct child pages.
A piece of content has different types of descendants, depending on its type:
page: descendant is page, comment, attachment
blogpost: descendant is comment, attachment
attachment: descendant is comment
comment: descendant is attachment
The map will always include all descendant types that are valid for the content. However, if the content has no instances of a descendant type, the map will contain an empty array for that descendant type.
Returns all descendants of a given type, for a piece of content. This is similar to Get content children by type, except that this method returns child pages at all levels, rather than just the direct child pages.
A piece of content has different types of descendants, depending on its type:
page: descendant is page, comment, attachment
blogpost: descendant is comment, attachment
attachment: descendant is comment
comment: descendant is attachment
Custom content types that are provided by apps can also be returned.
POST /wiki/rest/api/content/{id}/pagehierarchy/copy
CopyHierarchy allows the copying of an entire hierarchy of pages and their associated properties, permissions and attachments.
The id path parameter refers to the content id of the page to copy, and the new parent of this copied page is defined using the destinationPageId in the request body. The titleOptions object defines the rules of renaming page titles during the copy; for example, search and replace can be used in conjunction to rewrite the copied page titles.
CopyPage copies a single page and its associated properties, permissions, attachments, and custom contents. The id path parameter refers to the content ID of the page to copy. The target of the page to be copied is defined using the destination in the request body and can be one of the following types.
space: page will be copied to the specified space as a root page on the space
parent_page: page will be copied as a child of the specified parent page
existing_page: page will be copied and replace the specified page
By default, the following objects are expanded: space, history, version.