Recent alerts, resolved ones included, and whether anybody was told

GET /v1/admin/health/alerts answers "what is open". This answers the two questions it cannot. First, what fired and then went away: a row with a resolved_at is the evidence that something was broken for six hours this morning, which is the question an operator asks afterwards. Second, whether a HUMAN was told — notifications is every operator email this deployment has produced, with its dedupe key and its delivery status, so "the alert row exists but the digest was suppressed because EMAIL_ENABLED is false" is readable rather than deducible. No customer identifier, query or address appears in it; the recipient is held as a hash, as everywhere in this lane.

get/v1/admin/alerts/recent

Request

Base URL: https://api.hyperresearch.ai
URL: https://api.hyperresearch.ai/v1/admin/alerts/recent
Auth: API key in cookie hr_session

Response

Recent alerts and the operator emails about them

as_ofstring required

email_configuredboolean required

Whether OPERATOR_ALERT_EMAIL holds an address. False means the operator lane is off and nobody is being told anything, whatever the rows below say.

email_enabledboolean required

Whether this deployment would actually send: EMAIL_ENABLED=true plus a key plus a from-address. False means the rows below were written and suppressed.

Changes

No recorded changes to this operation across all 1 revision of this API.