List the life events of a vault
List the life events of a vault, the most recent first.
Deleted life events are left out. Narrow the list to one person with contact.
The value of a sensitive field comes back as null, with is_hidden set to true, unless the key holds the sensitive-fields scope.
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 the life events live in, named either by the readable name it reports as slug or by its id.
Only the life events this contact took part in, named by its slug or its id. A contact of another vault answers 404.
Which page to answer with.
How many records one page holds, between 1 and 100. A number outside the range is brought back into it rather than refused.
Returns
A page of life event objects, and how many there are in all. A vault of another account answers 404.
The life events on this page. An empty list rather than an error when there are none.
One life event.
Always life_event. 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 life event is called: its title, or the name of its type when it has none.
The title written for it, or null.
Its type. A type deleted since still names the life events recorded as it.
The id of the type, as the life event types endpoints give it.
What the type is called.
The group it was recorded on, as an object holding its id and its name, or null when it was not recorded on a group or the group has been deleted.
The day it happened, written as a year, a month and a day.
How long it lasted, in minutes, or null.
What was written about it, or null.
Where it happened, or null.
The contacts who were there, in order. The first is the person the life event is recorded for.
One contact who was there.
The id of the contact.
The name the contact is shown under.
Where the contact stands in the list, counting from 0.
The values of the custom fields its type asks for. 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 life event is updated.
How the field is named in an import or an export. It is unique inside its group only.
What the field is called on the life event.
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 contact page 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.
Where it was written from: contact, dashboard, group, api, mcp, day, import or module.
When it was deleted, as a count of seconds since 1970, or null.
When it was written down, as a count of seconds since 1970.
When it last changed, as a count of seconds since 1970.
Where to find this record.
The absolute address this record is read from.
The page of the contact the life event is recorded for, whose timeline shows it, in the application. It is the link to give a person.
Where you are in the collection.
The page this is, counting from 1.
How many one page holds, which is the size that was asked for once it has been brought into the allowed range.
How many life events there are in all, not how many are on this page.
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.