Rename or move a folder
Rename a folder, move it among the folders of the vault, or both.
A field left out keeps its value, and a name left empty once markup is stripped keeps the one the folder had. The other folders shift so the positions run from 1 without a gap.
The change is written to the account log.
Parameters
Sent as JSON. Anything not listed here is ignored.
The vault, named either by the readable name it reports as slug or by its id. A vault of another account answers 404.
The id of the folder. A folder of another vault or of another account answers 404.
The new name, up to 255 characters.
Where the folder goes, 1 for first. A number past the end puts it last.
Returns
The knowledge folder object as it now reads. A folder of another vault or of another account answers 404.
The knowledge folder.
Always knowledge_folder.
The id of the folder, which every address naming it takes.
Everything the folder holds.
What the folder is called.
Where the folder stands among the folders of the vault, from 1.
How many notes the folder holds.
How many lists the folder holds.
The notes the folder holds.
One note.
The id of the note, which the notes endpoints take.
The title of the note.
The lists the folder holds.
One list.
The id of the list, which the lists endpoints take.
The title of the list.
When the folder was added, as a count of seconds since 1970.
When it last changed, as a count of seconds, or null.
Where to find the folder. A folder is not read on its own, so it has no address of its own.
The Knowledge screen of the vault in the application, which opens for somebody signed in rather than for a key.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.