MUmultigest
Alert Recipients

Remove a platform alarm recipient

Changed on

Soft delete.

Deliberately NOT blocked when it removes the last recipient: the resolver is contractually never-empty (it falls back and logs ERROR), so an empty table degrades loudly rather than silently alerting nobody. A hard block here would instead strand an operator who wants to swap the whole list.

delete/api/admin/alert-recipients/{recipient_id}

Request

  • Base URL
    https://api.multigest.pt (the document declares no server; this is the origin it was published from)
  • URL
    https://api.multigest.pt/api/admin/alert-recipients/{recipient_id}
  • Auth
    API key in header x-api-token and API key in header x-origin-verify

Path parameters

recipient_idinteger required

Headers

x-api-tokenstring nullable

Response

Successful Response

unknown required

Changes