Add a folder
Add a folder to a vault's Knowledge, after the folders already there.
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.
What the folder is called, up to 255 characters. Markup is stripped, and a name left empty once it is stripped is refused with “Give the folder a name.”
Returns
The knowledge folder object that was added.
The knowledge folder, which holds nothing yet, so its notes and lists are empty.
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.
The lists the folder holds.
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.