Alert Recipients
List platform alarm recipients
Changed onEvery recipient, with suppressed marking addresses AWS SES refuses.
The suppression lookup is batched (ONE query for the whole page) and app/db/email_suppression.py::get_suppressed_subset fails OPEN - an empty set on error, so a DB hiccup renders the page without badges instead of claiming everyone is broken. It is deliberately NOT done on the send path: is_suppressed() fails CLOSED and opens a connection per address, which on the alarm path would silence the alert reporting the outage.
get/api/admin/alert-recipients
Request
- Base URLhttps://api.multigest.pt (the document declares no server; this is the origin it was published from)
- URLhttps://api.multigest.pt/api/admin/alert-recipients
- AuthAPI key in header x-api-token and API key in header x-origin-verify
Headers
x-api-tokenstring nullable
Response
Successful Response
unknown required
Changes
- info
endpoint added
- info