Alerts
What needs a decision today: overdue contract milestones, stock below its reorder point, quarantined lots. Deduplicated per rule, subject and day, so the same alert does not arrive every morning until somebody mutes it.
1 operation in the alerts namespace.
alerts.listAlerts
Section titled “alerts.listAlerts”List what needs attention
POST /rpc/v1/alerts.listAlertsAlso available as GET with a URL-encoded input query parameter, so the response can be HTTP-cached.
The live scan, not the digest log. An alert emailed this morning and resolved at ten is no longer outstanding and is not returned — notifiedAt says whether a digest has already carried it today.
Requires permission alerts.read and the core module on the organization’s plan.
Request
Section titled “Request”| Field | Type | Required | Description |
|---|---|---|---|
filter |
object | no |
Example
Section titled “Example”curl -X POST https://api-staging.roastery.run/rpc/v1/alerts.listAlerts \ -H "Authorization: Bearer $ROASTERY_API_KEY" \ -H "X-Roastery-Org: $ORG_ID" \ -H "Content-Type: application/json" \ -d '{}'