Alerts define notification rules that tell Secureagentics where and how to deliver notifications when specific conditions are met — such as a policy violation, a detected anomaly, or an agent going offline. You can route alerts to email, Slack, or any HTTP webhook endpoint.Documentation Index
Fetch the complete documentation index at: https://docs.adrian.secureagentics.ai/llms.txt
Use this file to discover all available pages before exploring further.
Create an alert
POST /v1/alerts
Creates a new alert and returns the alert object. Once created, the alert is active immediately and will trigger notifications when its conditions are matched.
Request body
Human-readable name for the alert, unique within your account.
The kind of event that triggers this alert. One of:
policy_violation, anomaly_detected, agent_down, rate_limit_exceeded.The delivery channel for notifications. One of:
email, slack, webhook.The delivery target for the channel. Provide an email address for
email, a Slack incoming webhook URL for slack, or an HTTPS URL for webhook.Optional filters that narrow when the alert fires. Supported filter keys:
agent_id(string) — Only trigger for events from this agent.severity(string) — Only trigger for events at or above this severity level. One of:low,medium,high,critical.
Scope the alert to a specific agent. Equivalent to setting
conditions.agent_id. If both are provided, conditions.agent_id takes precedence.Response fields
Unique alert identifier, prefixed with
alr_.The alert name.
The event type that triggers the alert.
The delivery channel:
email, slack, or webhook.The delivery target for the channel.
The filter conditions configured for this alert.
The agent this alert is scoped to, or
null if it applies to all agents.ISO 8601 timestamp of when the alert was created.
Current alert status. One of:
active, inactive.cURL
List alerts
GET /v1/alerts
Returns a paginated list of all alerts configured in your account.
Query parameters
Maximum number of alerts to return per page. Accepted range: 1–100.
Number of alerts to skip before returning results. Use for pagination.
Response fields
Array of alert objects.
Total number of alerts in your account, regardless of pagination.
cURL
Delete an alert
DELETE /v1/alerts/{id}
Permanently deletes an alert. Once deleted, the alert stops firing and no further notifications are sent. Returns 204 No Content on success.
Path parameters
The alert ID, prefixed with
alr_.cURL