Get Alert Rule
developer/v1/alerts/rules/:idRetrieves the complete configuration, current status, and metadata of a specific alert rule. Includes the rule's trigger conditions, notification channels, cooldown settings, and the timestamp of when it was last triggered.
What It Does
Returns the full configuration of an alert rule identified by its ID, scoped to the authenticated organization. Includes all threshold settings, notification channel configuration, enabled/disabled state, and the last triggered timestamp for understanding alert frequency.
Why It's Useful
Essential for debugging alert behavior — verify thresholds, check if a rule is in cooldown, and confirm notification channels are correctly configured. Use before on-call rotations to ensure critical rules are active and properly tuned.
Use Cases
Alert Debugging
Investigate why an SSL expiry alert fired early or why expected DNS change alerts are not triggering by checking threshold values and cooldown status.
Quickly diagnose misconfigured or misfiring alert rules.
Pre-On-Call Verification
Before starting an on-call shift, verify that critical alert rules are enabled and thresholds are reasonable.
Start on-call shifts with confidence that alerting is properly configured.
Compliance Evidence
Document alert rule configurations as evidence of proactive monitoring for SOC 2 or ISO 27001 audits.
Provide auditors with detailed proof of continuous monitoring controls.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | Required | Alert rule IDExample: rule_abc123 |
Response Fields
| Field | Type | Description |
|---|---|---|
rule.id | string | Alert rule ID |
rule.alert_type | string | Alert type identifier |
rule.enabled | boolean | Active monitoring state |
rule.threshold_value | number | Trigger threshold |
rule.threshold_window_minutes | number | Evaluation window in minutes |
rule.channels | array | Notification delivery channels |
rule.cooldown_minutes | number | Cooldown between alerts |
rule.last_triggered_at | string|null | Last trigger timestamp (ISO 8601) |
Code Examples
curl "https://api.edgedns.dev/v1/alerts/rules/:id" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d "domain=rule_abc123"const response = await fetch(
'https://api.edgedns.dev/v1/alerts/rules/:id?domain=rule_abc123',
{
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/:id',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
params={
'domain': 'rule_abc123'
}
)
data = response.json()
print(data)Read the full Get Alert Rule 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 Get Alert Rule endpoint live in the playground.