Update a record
Correct the name of a record and the values its template holds.
What you leave out is kept: a name not sent stays as it is, and so does every field not named in fields. A field sent as null is emptied.
The record stays on the template version it was written on. Only the fields of that version can be written, and each value is checked against what its field accepts.
A name sent empty answers 422 on name. A value refused by its field answers 422 on that field, and a required field emptied answers 422 on fields.
Parameters
Sent as JSON. Anything not listed here is ignored.
The vault the record lives in, named either by the readable name it reports as slug or by its id. Both answer.
The id of the record, as the list of records gives it.
What the record is called, up to 255 characters. It cannot be emptied.
The values to write, keyed by the id of the field they fill in, as the fields of the record give it. A repeating group takes a list of repetitions, each holding its id when it already exists and its values keyed by the ids of the fields inside the group.
The label picked beside a value, keyed by field id, for a field that carries one.
The wording typed when the picked label is the open one, keyed by field id.
True for a recurring date whose year nobody knows, keyed by field id.
True for a recurring date whose month nobody knows, keyed by field id.
Returns
The entity object as it now reads. A record in another vault, or belonging to somebody else, answers 404.
The record.
Always entity. 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.
What the record is called, up to 255 characters. It is how the record is listed and sorted, and it is reduced to plain text when it is written down.
The kind of record it is. It never changes.
The first letter of the first two words of the name, drawn on the generated avatar.
The background the generated avatar is drawn on. It is picked when the record is written down and kept afterwards.
The picture standing in for the record, with its id and url, or null when it is drawn as its initials.
Whether the record was put away. An archived record is still listed.
The exact version of the template the record was written on. A record stays on that version until somebody moves it.
The name of the template that version belongs to.
The values the record holds, in no particular order. A field left empty is not listed.
One value.
The id of the field, which is the key a value is written under when the record is updated.
How the field is named in an import or an export. It is unique inside its section only.
What the field is called on the record.
The kind of field: text, date, select, address and so on.
For a field inside a repeating group, the id of the repetition it belongs to, which is the id an update keeps that repetition by. Null otherwise.
The value, written as the page of the record shows it. A file field gives the name of the file. Null when hidden.
Whether the value was held back because the field is sensitive and the key does not hold the sensitive-fields scope.
When the record was written down, as a count of seconds since 1970.
When it last changed, as a count of seconds, or null.
Where to find this record.
The absolute address this record is read from.
The page of the record 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.