Skip to main content
POST
Move content tree node

Authorizations

Authorization
string
header
default:App
required

This is the most secure authorization type and the one with the most flexibility.

API keys can be generated by calling the dedicated API method. Furthermore, API keys can have a limited scope and cover only some API methods. Lastly, they can be revoked at any time. This range of possibilities makes API keys well suited for separating the API access rights across multiple applications or use cases. Finally, the loss of an API key is easily manageable.

You can manage your API keys from GUI, or programmatically with dedicated API.

API key Authorization header example:

Path Parameters

nodeId
string<uuid>
required

Unique identifier of the node to move.

Body

application/json
position
enum<string>
required

Position relative to the target node.

Available options:
ABOVE,
BELOW,
APPEND
Example:

"BELOW"

targetNodeId
string<uuid>
required

Identifier of the target node for relative positioning.

Example:

"3fa85f64-5717-4562-b3fc-2c963f66afa6"

Response

Content tree node moved successfully