Get Alert Details

developer

GET/v1/alerts/history/:id

Retrieves complete details of a specific triggered alert including the trigger data, message, lifecycle status, and timestamps for each state transition (triggered → acknowledged → resolved). Provides the full context needed for incident investigation, compliance documentation, and post-mortem analysis.

What It Does

Returns the full alert record by ID: alert type, rule that triggered it, trigger message with specific metric values (e.g., "SSL certificate expires in 14 days"), current status, and all lifecycle timestamps. Includes structured details with metadata about the conditions that caused the trigger.

Why It's Useful

Get the complete picture of any alert for debugging, compliance, or learning. The alert detail view answers three critical questions: What happened? When did we know? How long did it take to fix? This information is essential for ITIL-compliant incident records and SOC 2 audit trails.

Use Cases

DevOps Engineer

Incident Investigation

Examine the exact trigger conditions — was the SSL certificate at 14 days or 7 days? What was the error rate when the spike alert fired?

Understand precisely what triggered an alert to guide remediation.

Compliance Officer

Compliance Documentation

Export alert details with full timestamps as evidence that security events were detected and responded to within SLA.

Meet audit requirements for incident detection and response documentation.

SRE

Post-Mortem Analysis

Review the alert timeline to understand detection-to-acknowledgment and acknowledgment-to-resolution times for process improvement.

Identify opportunities to improve incident response workflows.

Parameters

Name	Type	Required	Description
`domain`	string	Required	Alert ID (from alert history list)Example: `alert_xyz789`

Response Fields

Field	Type	Description
`alert.id`	string	Alert ID
`alert.rule_id`	string	ID of the rule that triggered this alert
`alert.alert_type`	string	Alert type (e.g., ssl_expiry, dns_changed)
`alert.status`	string	Current lifecycle status
`alert.message`	string	Detailed trigger message with specific values
`alert.details`	object\|null	Structured trigger metadata
`alert.triggered_at`	string	When the alert fired
`alert.acknowledged_at`	string\|null	When someone acknowledged it
`alert.resolved_at`	string\|null	When it was resolved

Code Examples

cURL

curl "https://api.edgedns.dev/v1/alerts/history/:id" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d "domain=alert_xyz789"

JavaScript

const response = await fetch(
  'https://api.edgedns.dev/v1/alerts/history/:id?domain=alert_xyz789',
  {
    headers: {
      'Authorization': 'Bearer YOUR_API_KEY'
    }
  }
);

const data = await response.json();
console.log(data);

Python

import requests

response = requests.get(
    'https://api.edgedns.dev/v1/alerts/history/:id',
    headers={'Authorization': 'Bearer YOUR_API_KEY'},
    params={
    'domain': 'alert_xyz789'
    }
)

data = response.json()
print(data)

Read the full Get Alert Details 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

Alert History

List triggered alerts with filtering by status, type, and time range

Acknowledge Alert

Mark an alert as acknowledged with optional notes

External References

Learn more about the standards and protocols behind this endpoint.

NIST Alerting Guidelines Alerting Best Practices

Try This Endpoint

Test the Get Alert Details endpoint live in the playground.

Open in Playground Get API Key