API v1
v1
View as Markdown

List a contact's reminder dates

GET /api/v1/vaults/{vault}/contacts/{contact}/reminder-occurrences

List the dates the reminders about a contact produced, with what was answered for each.

Without a category, every date is listed, newest first, so any date can be looked up: remembered, forgotten, or never answered.

upcoming lists the next date of each active reminder. A date too far off to have been generated yet comes back with a null id, and cannot be answered, which nothing upcoming can be anyway.

history lists the answered dates, the latest answer first, including those of reminders deleted since.

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.

vault string Required

The vault the contact lives in, named either by the readable name it reports as slug or by its id.

contact string Required

The contact the reminders are about, named either by its slug or by its id. A contact addressed through the wrong vault answers 404.

category string Optional

One of overdue, today, upcoming or history.

page integer Optional default: 1

Which page to answer with.

per_page integer Optional default: 25

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 reminder date objects, and how many there are in all.

data array

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

data[] object

One date.

data[].type string

Always reminder_occurrence. 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.reminder uuid

The reminder this date belongs to.

data[].attributes.name string

What the reminder says.

data[].attributes.group object

The group the reminder is about, as an object holding id and name. Always null here, since these dates belong to reminders about a contact.

data[].attributes.date string

The day it falls on, written as a year, a month and a day, in the reminder's time zone.

data[].attributes.scheduled_for timestamp

The instant it is told at, as a count of seconds since 1970.

data[].attributes.category string

Where it stands while it waits for an answer, read against today in your time zone: upcoming before its day, today on its day, overdue from the day after. Null once it is answered or cancelled.

data[].attributes.answer string

What you said about this date: remembered or forgotten. Null while nobody answered. No answer is ever filled in for you, and a notification sent or read never counts as one.

data[].attributes.answered_at timestamp

When the answer was given, as a count of seconds, or null.

data[].attributes.cancelled_reason string

Why the date will not be asked about any more: rule_deleted, record_archived, record_deleted, field_removed, value_cleared, source_changed or rule_changed. Null otherwise. A cancelled date is never counted as forgotten.

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 dates there are in all, not how many are on this page.

data[].links object

Where to find what this date belongs to.

data[].links.reminder string

The absolute address of the reminder, or null once the reminder was deleted.

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/vaults/dunder-mifflin/contacts/pam-beesly/reminder-occurrences?category=history \
-H "Authorization: Bearer $MONICA_TOKEN"
const response = await fetch('https://my.monicahq.com/api/v1/vaults/dunder-mifflin/contacts/pam-beesly/reminder-occurrences?category=history', {
headers: { Authorization: `Bearer ${token}` },
})
const data = await response.json()
$response = Http::withToken($token)->get('https://my.monicahq.com/api/v1/vaults/dunder-mifflin/contacts/pam-beesly/reminder-occurrences?category=history');
Response 200
{
"data": [
{
"type": "reminder_occurrence",
"id": "a9d3f6e1-2b47-4c08-8e5a-17f4c0b9d262",
"attributes": {
"reminder": "4e7b2c90-3d15-4a86-9f21-8b0c6e5d7a13",
"name": "Ask how the art school application went",
"group": null,
"date": "2026-09-14",
"scheduled_for": 1789390800,
"category": null,
"answer": "remembered",
"answered_at": 1789394400,
"cancelled_reason": null
},
"links": {
"reminder": "https://my.monicahq.com/api/v1/vaults/dunder-mifflin/contacts/pam-beesly/reminders/4e7b2c90-3d15-4a86-9f21-8b0c6e5d7a13"
}
}
],
"meta": {
"page": 1,
"per_page": 25,
"total": 1
}
}

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