The API has no way to set a page or folder's position within the table of contents tree. parent_id controls nesting, but not order among siblings. Reordering only works by manually dragging in the UI.
Teams automating knowledge setup can't fully script their structure. Anything needing a specific order requires manual cleanup after every API-driven creation.
Add a position parameter to the update a note endpoint
The API can't set the order of KB pages and folders. Because of that, we move thousands of pages by hand with drag-and-drop every time we restructure a knowledge base. This is slow and error-prone, and it blocks us from automating KB publishing and migrations.
What we need is API support for:
Setting the position of a page or folder among its siblings
Moving a page or folder to a different parent