List the lists of a vault
List the lists of a vault's Knowledge by title, without their columns and items.
This endpoint also answers QUERY, with the same parameters sent in the request body. How QUERY works.
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.
Only the lists of this folder. The id of a folder of the vault, as the knowledge folders endpoints give it. A folder of another vault answers 404.
Returns
Every knowledge list object of the vault, without its columns and items, or an empty list. A vault of another account answers 404.
Every one of the lists, whole rather than a page at a time.
One knowledge list, without its columns and items.
Always knowledge_list. It names the kind of record, so a caller holding several kinds can tell them apart without looking at where they came from.
The id of this record, as a string even when it reads as a number. It is what every endpoint naming this record takes.
Everything the record holds.
The title of the list.
What the list is for, in Markdown as written, or null.
The folder the list sits in.
The id of the folder, as the knowledge folders endpoints give it.
What the folder is called.
When the list was started, as a count of seconds since 1970.
When it, one of its columns or one of its items last changed, as a count of seconds, or null.
Where to find this record.
The absolute address this record is read from.
The list in the application, which opens for somebody signed in rather than for a key. It is the link to give a person.
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.