---
title: On-Call Integrations
description: >-
  Trigger Datadog On-Call Pages from third-party monitoring, alerting, and
  incident tools using native integrations or a generic webhook.
breadcrumbs: Docs > Incident Response > On-Call > On-Call Integrations
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# On-Call Integrations

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com, us2.ddog-gov.com

{% alert level="danger" %}
This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site.md). ({% placeholder "user-datadog-site-name" /%}).
{% /alert %}

{% /callout %}

## Overview{% #overview %}

Datadog On-Call supports multiple triggering sources beyond native Datadog monitors. Use third-party monitoring, alerting, and incident management tools to send Pages directly to your On-Call Teams. Alerts from any part of your stack then reach the right responders through your configured escalation policies. For more information, see [Trigger a Page](https://docs.datadoghq.com/incident_response/on-call/pages.md#trigger-a-page).

Each native integration listed on this page includes setup instructions on its own integration tile. These instructions cover how to configure the third-party tool to send a Page. They also cover how to map its alerts to a Datadog On-Call Team. If your tool doesn't have a native integration, use the generic webhook integration instead.

## Available integrations{% #available-integrations %}

Datadog On-Call includes native paging support for the following tools:


## Preview integrations{% #preview-integrations %}

The following integrations are available as a [Preview](https://www.datadoghq.com/product-preview/on-call-integrations/). Select a tile to request access.


## Generic webhook integration{% #generic-webhook-integration %}

If your tool is not listed, use the [Datadog Events API](https://docs.datadoghq.com/api/latest/events/post-an-event.md) to trigger On-Call Pages from any source that can make an HTTP request.

Post an event with the following parameters:

| Parameter       | Value                                                                                                                                                                                                                                                                          |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| aggregation_key | A unique, user-defined identifier for the alert. Datadog uses this value for deduplication: If an incoming alert's `aggregation_key` matches an already triggered Page, Datadog doesn't create a Page. Datadog also uses this value to link a recovery event to its open Page. |
| category        | The type of event. Set to `alert` to trigger a Page.                                                                                                                                                                                                                           |
| text            | The body of the alert message. Include `@oncall-<TEAM_HANDLE>` to route the Page to the correct On-Call Team.                                                                                                                                                                  |
| title           | A short summary of the alert. Displayed as the Page's title.                                                                                                                                                                                                                   |

The `@oncall-<TEAM_HANDLE>` mention in `text` determines which On-Call Team receives the Page. Replace `<TEAM_HANDLE>` with your team's handle as configured in Datadog.

{% collapsible-section %}
#### Example: Request body

```json
{
  "data": {
    "attributes": {
      "aggregation_key": "alert_unique_identifier",
      "attributes": {
        "priority": "1",
        "status": "error"
      },
      "category": "alert",
      "message": "@oncall-database Something is broken!",
      "title": "High memory usage"
    },
    "type": "event"
  }
}
```

{% /collapsible-section %}

## Further reading{% #further-reading %}

Additional helpful documentation, links, and articles:

- [Datadog On-Call](https://docs.datadoghq.com/incident_response/on-call.md)
- [Pages](https://docs.datadoghq.com/incident_response/on-call/pages.md)
- [Routing Rules](https://docs.datadoghq.com/incident_response/on-call/routing_rules.md)