Send Alerts from Any Monitoring Tool to Alert24

When your monitoring tool fires an alert, Alert24 can automatically open a tracked incident — with severity mapping, deduplication, and routing to your on-call schedule. No more manually creating incidents after your pager goes off.

How it works

Each monitoring tool has a mechanism to send an HTTP webhook when an alert fires. Alert24's incidents API accepts that webhook (either directly or via a small adapter) and creates a tracked incident in your account. When the alert resolves, the incident can auto-close.

Every incident created this way:

• Routes through your escalation policies
• Deduplicates on a stable alias so repeated alerts don't create duplicates
• Appears in your incident timeline alongside manually created incidents
• Can auto-link to affected services

Supported tools

The incidents API

All integrations ultimately POST to the same endpoint:

POST https://app.alert24.net/api/v1/incidents
Authorization: Bearer ak_live_YOUR_KEY
Content-Type: application/json

{
  "title": "Your alert title",
  "severity": "critical",
  "alias": "unique-dedup-key",
  "source": "your-tool-name"
}

See the Incidents API reference for the full field list.

Deduplication

Set the alias field to a stable identifier for the alert (e.g., nagios-hostname-servicename, datadog-alert-12345). If the same alert fires multiple times, Alert24 increments the occurrence count on the existing open incident rather than creating duplicates. This is the most important field to get right.

Any tool not listed?

If your monitoring tool can POST a JSON webhook, it can send incidents to Alert24. Point it at POST /api/v1/incidents with an Authorization: Bearer header and a JSON body containing at least "title". The curl / API guide shows the raw request format.