List Alert Rules
developer/v1/alerts/rulesRetrieves all alert rules configured for your organization. Returns each rule's configuration, enabled status, last triggered time, and notification channels. Supports filtering by alert type and enabled status to help audit monitoring coverage across your infrastructure.
What It Does
Returns a list of all alert rules belonging to the authenticated organization, ordered by creation date (newest first). Each rule includes its full configuration: alert type, threshold, channels, cooldown period, and last trigger timestamp. Filter by enabled status or alert type to narrow results.
Why It's Useful
Provides a complete inventory of your monitoring configuration for coverage audits and gap analysis. Identify which domains lack SSL expiry alerts, which alert types are generating the most triggers, and which rules may need threshold adjustments. Essential for maintaining a healthy alerting posture — a core SRE practice for reducing alert fatigue.
Use Cases
Monitoring Coverage Audit
Review all active alert rules to verify every production domain has SSL expiry, DNS change, and security score monitoring configured.
Identify monitoring gaps before they lead to missed incidents.
Alert Rule Cleanup
Filter by enabled=false to find paused rules that should be re-enabled or permanently deleted after maintenance windows.
Reduce configuration drift and keep alerting lean.
Dashboard Integration
Fetch all alert rules to display in a custom monitoring dashboard alongside uptime metrics and incident history.
Build integrated operational dashboards with full monitoring context.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
type | string | Optional | Filter by alert type (e.g., ssl_expiry, dns_changed)Example: ssl_expiry |
Response Fields
| Field | Type | Description |
|---|---|---|
rules | array | List of alert rule objects |
total | number | Total number of rules matching filters |
Code Examples
curl "https://api.edgedns.dev/v1/alerts/rules" \
-H "Authorization: Bearer YOUR_API_KEY"const response = await fetch(
'https://api.edgedns.dev/v1/alerts/rules',
{
headers: {
'Authorization': 'Bearer YOUR_API_KEY'
}
}
);
const data = await response.json();
console.log(data);import requests
response = requests.get(
'https://api.edgedns.dev/v1/alerts/rules',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
params={
}
)
data = response.json()
print(data)Read the full List Alert Rules guide
Why it matters, real-world use cases, parameters, response fields, and how to call it from Claude, ChatGPT, or Gemini via MCP.
Read the guide →Related Endpoints
External References
Learn more about the standards and protocols behind this endpoint.
Try This Endpoint
Test the List Alert Rules endpoint live in the playground.