API v1
v1
View as Markdown

Delete a life event type

DELETE /api/v1/life-event-types/{lifeEventType}

Remove a nature you added.

A nature the product supplied stays, because the wording it falls back to belongs to the product. Retire it instead: it leaves the choice offered when a life event is recorded, and everything already written keeps reading as it did.

A deletion is recoverable, so an accident is not the end of anything. The custom fields the nature asked for are deliberately left where they are, so a restored nature comes back asking for what it asked for.

Path parameters

Sent as JSON. Anything not listed here is ignored.

lifeEventType uuid Required

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

Returns

Nothing. A nature the product supplied answers 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-types/8b2e5c70-1a94-4f38-b6d2-0e7c94a35f18 \
-X DELETE \
-H "Authorization: Bearer $MONICA_TOKEN"
const response = await fetch('https://my.monicahq.com/api/v1/life-event-types/8b2e5c70-1a94-4f38-b6d2-0e7c94a35f18', {
method: 'DELETE',
headers: { Authorization: `Bearer ${token}` },
})
$response = Http::withToken($token)->delete('https://my.monicahq.com/api/v1/life-event-types/8b2e5c70-1a94-4f38-b6d2-0e7c94a35f18');
Response 204
[]

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