List notifications with pagination and filters
Everything this company sent, newest first — including the rescue emails the platform sent on its behalf.
Rows with is_owner_fallback: true are not alerts you asked for. They are the umbrella guarantee at work: an alert reached nobody, so the account owner was emailed that delivery failed. They are listed rather than hidden because an email really did go out, and hiding it would be its own lie — but they must not be counted as delivered alerts. Their recipient is the internal "Owner (fallback delivery)" one, flagged is_system: true; that recipient never appears in GET /recipients and is not a missing person. The alert each rescue is about carries delivered_via_owner_fallback: true in its own metadata and stays failed.
Request
- Base URL: https://wardenpoint.com (the document declares no server; this is the origin it was published from)
- URL: https://wardenpoint.com/api/v1/notifications
- Auth: API key in header X-API-Key
Query parameters
Lifecycle state of a notification. FOUR of the seven are terminal and will never change again: completed, failed, cancelled, acknowledged. Poll until you see one of those four — waiting only for completed or failed hangs until your own timeout on every alert a human confirms.
pending — created, waiting for a worker. Not terminal. processing — a worker is delivering it right now. Not terminal. escalating — delivery happened, nobody confirmed in time, and the escalation chain is walking to the next person. Not terminal: it still ends in acknowledged or failed. completed — delivered. TERMINAL. failed — every channel and attempt was exhausted without delivery. TERMINAL, and the only status retry accepts. cancelled — stopped before delivery, by the cancel endpoint. TERMINAL. acknowledged — a human confirmed it and the escalation chain stopped. TERMINAL, and the outcome the product exists for: an alert that reaches this has done its job.
Filter by lifecycle status. Any value of the enum is accepted, including the terminal acknowledged.
Response
Paginated notifications. The paginator sits at the top level — data plus current_page, per_page, total, last_page — and each entry of data is exactly what the card and the status poll return for that notification.
Changes
No recorded changes to this operation across all 1 revision of this API.