API v1
v1
View as Markdown

Delete a reminder

DELETE /api/v1/vaults/{vault}/contacts/{contact}/reminders/{reminder}

Stop a reminder for good. There is no pause: deleting is the only way to stop one.

Nothing further is delivered, and the dates still waiting for an answer are dropped. The answers already given stay, and are still read from the dates endpoint.

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

reminder uuid Required

The id of the reminder. A reminder about somebody else answers 404, and so does a deleted one.

Returns

Nothing at all.

Rate limit

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

DELETE
curl https://my.monicahq.com/api/v1/vaults/dunder-mifflin/contacts/pam-beesly/reminders/4e7b2c90-3d15-4a86-9f21-8b0c6e5d7a13 \
-X DELETE \
-H "Authorization: Bearer $MONICA_TOKEN"
const response = await fetch('https://my.monicahq.com/api/v1/vaults/dunder-mifflin/contacts/pam-beesly/reminders/4e7b2c90-3d15-4a86-9f21-8b0c6e5d7a13', {
method: 'DELETE',
headers: { Authorization: `Bearer ${token}` },
})
$response = Http::withToken($token)->delete('https://my.monicahq.com/api/v1/vaults/dunder-mifflin/contacts/pam-beesly/reminders/4e7b2c90-3d15-4a86-9f21-8b0c6e5d7a13');
Response 204

No content.

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