List life event types
List every nature your account can record a life event as, grouped the way the picker groups them.
A nature is what a life event was: lunch, a phone call, a medical appointment, a concert. It carries a name, a sentence saying what it covers, a glyph, a tint, and the custom fields a life event of that nature asks for, which are read at their own address rather than here.
The list runs through the categories in the order you arranged them, and through the natures inside each category in the order you arranged those. Retired natures are listed with the rest, because one that is off is meant to be found again and switched back on.
A nature the product supplied reads in the language you ask for. Once somebody renames it, their words stand in every language.
This endpoint also answers QUERY, with the same parameters sent in the request body. How QUERY works.
Query parameters
Sent as JSON. Anything not listed here is ignored.
Which page to answer with.
How many natures 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 type objects, and how many there are in all.
The natures on this page. An empty list rather than an error when there are none.
One nature.
Always life_event_type. 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 category the nature is filed under. Moving a nature to another category is an ordinary change, and the life events recorded with it are regrouped along with it.
What the nature is called. One the product supplied reads in the language you ask for, until somebody renames it, after which their words stand in every language. Up to 255 characters, reduced to plain text, so no markup survives here.
A sentence saying what the nature covers, shown where somebody chooses one. Up to 255 characters, or null when nobody wrote one.
The glyph drawn beside the nature, chosen from the catalogue the product ships, or null to read by name alone.
The tint the nature is drawn in, chosen from the palette the product ships, or null to take the ordinary one.
Where the nature sits inside its category, counting from 1. Retired natures are numbered along with the rest, so one switched back on finds the place it had.
Whether the product supplied the nature with the account. It governs one thing and one thing only: a supplied nature cannot be deleted. It may be renamed, redrawn, moved and retired like any other.
Whether the nature is offered when a life event is recorded. False takes it out of that choice and touches nothing already written.
Whether a life event of this nature sets last_interaction_at, the Last in touch date, on the contacts it is recorded with. True for a moment shared with them, such as a call or a meal, and false for news about one of them, such as a move.
When the nature was added, as a count of seconds since 1970 rather than a written date.
When it last changed, as a count of seconds. Equal to created_at until it first changes.
Where to find this record.
The absolute address this record is read from.
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 natures 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.