Start a list
Start a list in a vault's Knowledge, with the columns Name and Note.
Every field is optional. A list without a title is called “Untitled list”. Without a folder it goes to the first folder of the vault, and a vault without any folder gets one called “General” to hold it. Rename, add or remove columns through the columns endpoints.
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 title of the list, up to 255 characters. Markup is stripped.
What the list is for, in Markdown, up to 5,000 characters.
The id of a folder of the vault, as the knowledge folders endpoints give it. A folder of another vault answers 404.
Returns
The knowledge list object that was started.
The knowledge list, which holds no item yet.
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.
The columns of the list, in their order. A list always has at least one.
One column.
The id of the column, which the columns endpoints and the cells of an item take.
What the column is called.
Where the column stands, from 1.
The items of the list, in their order.
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.