API v1
v1
View as Markdown

Answer a reminder date

PUT /api/v1/vaults/{vault}/contacts/{contact}/reminder-occurrences/{occurrence}/answer

Say whether you remembered a date or forgot it. The answer is final.

remembered is accepted from the date's own day. forgotten is accepted from the day after. Both are read against today in your time zone, and anything earlier answers 422.

An answer cannot be changed or taken back, and a second answer for the same date answers 422, whatever it says. A cancelled date answers 422 too.

Answering drops the notifications for that date not sent yet, and touches no other date: next year's birthday is still waiting.

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.

occurrence uuid Required

The id of the date.

answer string Required

remembered or forgotten.

Returns

The reminder date object, with its answer.

data object

The 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.

data.links object

Where to find what this date belongs to.

data.links.reminder string

The absolute address of the reminder.

Rate limit

Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.

PUT
curl https://my.monicahq.com/api/v1/vaults/dunder-mifflin/contacts/pam-beesly/reminder-occurrences/a9d3f6e1-2b47-4c08-8e5a-17f4c0b9d262/answer \
-X PUT \
-H "Authorization: Bearer $MONICA_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"answer": "remembered"
}'
const response = await fetch('https://my.monicahq.com/api/v1/vaults/dunder-mifflin/contacts/pam-beesly/reminder-occurrences/a9d3f6e1-2b47-4c08-8e5a-17f4c0b9d262/answer', {
method: 'PUT',
headers: { Authorization: `Bearer ${token}`, 'Content-Type': 'application/json' },
body: JSON.stringify({
answer: 'remembered',
}),
})
const data = await response.json()
$response = Http::withToken($token)->put('https://my.monicahq.com/api/v1/vaults/dunder-mifflin/contacts/pam-beesly/reminder-occurrences/a9d3f6e1-2b47-4c08-8e5a-17f4c0b9d262/answer', [
'answer' => 'remembered',
]);
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"
}
}
}

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