Acknowledge Alert
developer/v1/alerts/history/:id/acknowledgeMarks a pending alert as acknowledged, indicating that someone is aware of the issue and investigating. Optionally include notes describing the acknowledgment context. This stops repeat notifications and signals to the team that the alert is being handled — a critical step in the incident lifecycle used by tools like PagerDuty, OpsGenie, and Datadog.
What It Does
Transitions the alert status from "pending" to "acknowledged", records the acknowledgment timestamp, and stores optional notes. Only pending alerts can be acknowledged — attempting to acknowledge an already-acknowledged or resolved alert returns a validation error. This prevents duplicate state transitions and ensures clean audit trails.
Why It's Useful
Acknowledgment is the first step in structured incident response. It prevents multiple engineers from investigating the same issue (reducing duplication), stops notification escalation chains, and starts the clock on your acknowledgment-to-resolution SLA. Per SRE best practices, tracking Mean Time to Acknowledge (MTTA) helps identify response process bottlenecks.
Use Cases
On-Call Response
Acknowledge an SSL expiry alert to indicate you are handling the certificate renewal, with notes like "Initiating Let's Encrypt renewal for production domains".
Coordinate team response and prevent duplicate investigation.
Escalation Prevention
Acknowledge alerts within the SLA window to prevent automatic escalation to secondary on-call or management.
Keep incident handling at the appropriate tier without unnecessary escalations.
Shift Handoff
Review which alerts are pending vs. acknowledged during shift handoffs to ensure nothing falls through the cracks.
Seamless operational handoffs with clear ownership of each active alert.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | Required | Alert ID (path parameter). Optional JSON body with { "notes": "..." }Example: {"notes": "Investigating certificate renewal for example.com"} |
Response Fields
| Field | Type | Description |
|---|---|---|
acknowledged | boolean | true if successfully acknowledged |
Code Examples
curl "https://api.edgedns.dev/v1/alerts/history/:id/acknowledge" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d "domain={"notes": "Investigating certificate renewal for example.com"}"const response = await fetch(
'https://api.edgedns.dev/v1/alerts/history/:id/acknowledge?domain=%7B%22notes%22%3A%20%22Investigating%20certificate%20renewal%20for%20example.com%22%7D',
{
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/history/:id/acknowledge',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
params={
'domain': '{"notes": "Investigating certificate renewal for example.com"}'
}
)
data = response.json()
print(data)Read the full Acknowledge Alert 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 Acknowledge Alert endpoint live in the playground.