List the Knowledge of a vault
List every folder of a vault's Knowledge in its order, each with the ids and titles of its notes and lists.
It is the table of contents of the vault's Knowledge. Read a note or a list through its own endpoint.
This endpoint also answers QUERY, with the same parameters sent in the request body. How QUERY works.
Path 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.
Returns
Every knowledge folder object of the vault, or an empty list. A vault of another account answers 404.
Every folder of the vault, whole rather than a page at a time.
One 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.