Node Update Properties
Update the properties of a node. New schema fields will result in the schema of the node being updated before values are assigned. This will also propagate to all sibling nodes as they all share the same schema.
/nodes/{node_slug}/propertiesUpdate the properties of a node. New schema fields will result in the schema of the node being updated before values are assigned. This will also propagate to all sibling nodes as they all share the same schema.
In: cookie
Path Parameters
Unique node Slug.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Note: Properties are replace-all and are not merged with existing.
Response Body
application/json
application/json
curl -X PATCH "https://example.com/nodes/cc5lnd2s1s4652adtu50/properties" \ -H "Content-Type: application/json" \ -d '{ "properties": [ { "name": "string", "value": "string" } ] }'{
"properties": [
{
"fid": "cc5lnd2s1s4652adtu50",
"name": "string",
"type": "text",
"value": "string",
"sort": "string"
}
]
}{
"type": "string",
"title": "string",
"detail": "string",
"trace_id": "string",
"metadata": {}
}Node Update Position PATCH
Update the node's position in the tree, which optionally allows for changing the node's parent either to another node or to `null` which severs the parent and moves the node to the root. This endpoint also allows for moving the node's sort position within either its current parent, or when moving it to a new parent. Use this operation for a draggable tree interface or a table interface.
Node Update Property Schema PATCH
Updates the property schema of this node and its siblings. All children of a node use the same schema for properties resulting in a table-like structure and behaviour. Property schemas are loosely structured and can automatically cast their values sometimes. A failed cast will not change data and instead just yield an empty value when reading however changing the schema back to the original type (or a type compatible with what the type was before changing) will retain the original data upon next read. This permits clients to undo changes to the schema easily while allowing quick schema changes without the need to remove or update values before.