API v1
v1
View as Markdown

List life event categories

GET /api/v1/life-event-categories

List the categories your account files its life event natures under, in the order you arranged them.

A category groups the vocabulary in settings and pickers, filters the journal and gives aggregate statistics a level to count at. It never decides which fields a life event carries, who participated, or how it is shared. Moving a nature between categories changes how its life events are grouped, including past ones, and changes no recorded fact.

Every account starts with eight: Relationships and family, Work and education, Health and wellbeing, Home and daily life, Leisure and culture, Travel and experiences, Personal and Other. Other is the fallback, so a nature is never left unclassified. All eight are marked with is_system, which stops them being deleted and nothing else.

Retired categories are listed with the rest, because one that is off is meant to be found again and switched back on.

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.

page integer Optional default: 1

Which page to answer with.

per_page integer Optional default: 25

How many categories 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 category objects, and how many there are in all.

data array

The categories on this page. An empty list rather than an error when there are none.

data[] object

One category.

data[].type string

Always life_event_category. It names the kind of record, so a caller holding several kinds can tell them apart without looking at where they came from.

data[].id string

The id of this record, as a string even when it reads as a number. It is what every endpoint naming this record takes.

data[].attributes object

Everything the record holds.

data[].attributes.name string

What the category is called. A category 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.

data[].attributes.position integer

Where the category sits in the settings, the pickers and the journal filters, counting from 1. Retired categories are numbered along with the rest, so one switched back on finds the place it had.

data[].attributes.is_system boolean

Whether the product supplied the category with the account. It governs one thing and one thing only: a supplied category cannot be deleted. It may be renamed, moved and retired like any other.

data[].attributes.is_active boolean

Whether the category and the natures under it are offered when a life event is recorded. False removes the whole category from that choice and touches nothing already written.

data[].attributes.life_event_type_count integer

How many life event natures are filed under the category, retired ones counted. It is what decides whether the category may be deleted.

data[].attributes.created_at timestamp

When the category was added, as a count of seconds since 1970 rather than a written date.

data[].attributes.updated_at timestamp

When it last changed, as a count of seconds. Equal to created_at until it first changes.

data[].links object

Where to find this record.

data[].links.self string

The absolute address this record is read from.

meta object

Where you are in the collection.

meta.page integer

The page this is, counting from 1.

meta.per_page integer

How many one page holds, which is the size that was asked for once it has been brought into the allowed range.

meta.total integer

How many categories 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.

GET
curl https://my.monicahq.com/api/v1/life-event-categories \
-H "Authorization: Bearer $MONICA_TOKEN"
const response = await fetch('https://my.monicahq.com/api/v1/life-event-categories', {
headers: { Authorization: `Bearer ${token}` },
})
const data = await response.json()
$response = Http::withToken($token)->get('https://my.monicahq.com/api/v1/life-event-categories');
Response 200
{
"data": [
{
"type": "life_event_category",
"id": "5f8b3c21-9d07-4a64-8e12-7b0a4d6c3e95",
"attributes": {
"name": "Relationships and family",
"position": 1,
"is_system": true,
"is_active": true,
"life_event_type_count": 0,
"created_at": 1756252800,
"updated_at": 1756252800
},
"links": {
"self": "https://my.monicahq.com/api/v1/life-event-categories/5f8b3c21-9d07-4a64-8e12-7b0a4d6c3e95"
}
},
{
"type": "life_event_category",
"id": "a71d6e04-2b58-4c39-9f80-3e5c1a7b2d46",
"attributes": {
"name": "Volunteering",
"position": 9,
"is_system": false,
"is_active": true,
"life_event_type_count": 0,
"created_at": 1756339200,
"updated_at": 1756425600
},
"links": {
"self": "https://my.monicahq.com/api/v1/life-event-categories/a71d6e04-2b58-4c39-9f80-3e5c1a7b2d46"
}
}
],
"meta": {
"page": 1,
"per_page": 25,
"total": 2
}
}

Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.