API v1
v1
View as Markdown

Delete a relationship category

DELETE /api/v1/relationship-categories/{relationshipCategory}

Remove a category of your own that holds nothing.

Two categories cannot go. One the product supplied stays. One that still holds a type stays, and the answer says how many it holds, because removing it would take those types with it. Move them elsewhere first, or retire the category instead.

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

Path parameters

Sent as JSON. Anything not listed here is ignored.

relationshipCategory 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 type, 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/relationship-categories/b42e9c07-5a18-4d73-8e60-1c9f2b7a4d35 \
-X DELETE \
-H "Authorization: Bearer $MONICA_TOKEN"
const response = await fetch('https://my.monicahq.com/api/v1/relationship-categories/b42e9c07-5a18-4d73-8e60-1c9f2b7a4d35', {
method: 'DELETE',
headers: { Authorization: `Bearer ${token}` },
})
$response = Http::withToken($token)->delete('https://my.monicahq.com/api/v1/relationship-categories/b42e9c07-5a18-4d73-8e60-1c9f2b7a4d35');
Response 204
[]

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