Alerts are produced by the AgroPulse anomaly-detection engine whenever a sensor reading crosses a configured threshold. They can also be created manually — for example, to record an operator observation or to test notification delivery. Each alert carries a severity level, an optional title and type string, and a flag indicating whether it has been dispatched to recipients.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/diarpicu2022-commits/backend-AgroPulse/llms.txt
Use this file to discover all available pages before exploring further.
All list responses return alerts ordered by
createdAt descending, so the most recent alert is always first.Endpoints
List all alerts
Retrieves every alert in the system.alerts array.
Array of alert objects ordered by
createdAt descending.Create an alert
Posts a new alert record. Use this to inject manual observations or to trigger notification delivery outside of the automated pipeline.Full alert message describing the anomaly or event.
Short human-readable title for the alert.
Free-form category string (e.g.
"TEMPERATURE", "HUMIDITY").ID of the greenhouse this alert belongs to.
Whether the alert should be marked as already dispatched to recipients.
Severity level. Accepted values:
Invalid values are silently coerced to
| Value | Meaning |
|---|---|
INFO | Informational, no action required. |
WARNING | Condition requires attention. |
CRITICAL | Immediate intervention needed. |
INFO.Mark an alert as read
Acknowledges an alert by setting itsread flag to true.
The ID of the alert to acknowledge.
404 Not Found if no alert with the given ID exists.
Delete an alert
Permanently removes an alert record.The ID of the alert to delete.
{ "deleted": true } on success. Responds with 404 Not Found if the alert does not exist.