`GET /alerts` — the alerts you may see.
/alertsNewest first by the time each alert opened. Only alerts you may see. A page
may hold fewer than limit alerts, even none, while next_cursor is set:
follow it until it is null. There is no total.
Query Parameters
Comma-separated: one or more of open, acknowledged, resolved
One of informational, low, medium, high, critical
rule or system, or one origin: rule: or system:
The previous page's next_cursor
A whole number; 50 when absent, at most 100
int320 <= valueResponse Body
application/json
curl -X GET "https://example.com/alerts"{ "data": [ { "delivery_failed": [ "string" ], "description": "string", "first_seen": "string", "hit_count": 0, "id": "string", "key": "string", "last_seen": "string", "latest_row": null, "origin": "string", "severity": "informational", "source": { "class": "rule", "result_table_id": "string", "rule_id": "string", "run_id": "string" }, "status": "open", "title": "string" } ], "next_cursor": "string"}`GET /alerts/unopened` — the bell. GET
System alerts you have not opened, among the 50 newest system alerts; newest first; no cursor. Empty unless you are an org admin.
`POST /alerts/{id}/opened` — take a system alert off your own bell. POST
Changes nothing anyone else sees, so it needs `alerts:read`. A repeat succeeds; on a rule alert it does nothing.