API v1
v1
View as Markdown

Delete a life event category

DELETE /api/v1/life-event-categories/{lifeEventCategory}

Remove a category you added that holds nothing.

Two categories cannot go. One the product supplied stays, because the wording it falls back to belongs to the product. One that still holds natures stays, and the answer says how many, because removing it would take them with it. Move them elsewhere first, or retire the category instead.

Both refusals bite today, since natures are filed under categories from the moment an account is created.

A deletion is recoverable, so an accident is not the end of anything.

Path parameters

Sent as JSON. Anything not listed here is ignored.

lifeEventCategory uuid Required

The id of the category. A path that is not a uuid answers 404 without a query being run.

Returns

Nothing. A supplied category, and one still holding a nature, each answer 422 naming that reason, and one belonging to somebody else answers 404.

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/life-event-categories/a71d6e04-2b58-4c39-9f80-3e5c1a7b2d46 \
-X DELETE \
-H "Authorization: Bearer $MONICA_TOKEN"
const response = await fetch('https://my.monicahq.com/api/v1/life-event-categories/a71d6e04-2b58-4c39-9f80-3e5c1a7b2d46', {
method: 'DELETE',
headers: { Authorization: `Bearer ${token}` },
})
$response = Http::withToken($token)->delete('https://my.monicahq.com/api/v1/life-event-categories/a71d6e04-2b58-4c39-9f80-3e5c1a7b2d46');
Response 204
[]

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