---
title: Create notification endpoints
description: Create notification endpoints to send alerts on your time series data.
url: https://docs.influxdata.com/influxdb/v2/monitor-alert/notification-endpoints/create/
estimated_tokens: 755
product: InfluxDB OSS v2
version: v2
publisher: InfluxData
canonical: https://docs.influxdata.com/influxdb/v2/monitor-alert/notification-endpoints/create/
date: '2025-04-02T15:54:32-06:00'
lastmod: '2025-04-02T15:54:32-06:00'
---

This page documents an earlier version of InfluxDB OSS.[InfluxDB 3 Core](/influxdb3/core/) is the latest stable version.

#### API token hashing is enabled by default in InfluxDB OSS 2.9.0

Stronger token security: tokens are stored as hashes on disk, so a
copy of the database file doesn’t expose usable tokens. Existing
tokens are hashed on first startup and the original strings can’t
be recovered afterward — **capture any plaintext tokens you still
need before you upgrade**.

For more information, see [Token hashing](/influxdb/v2/admin/tokens/#token-hashing).

To send notifications about changes in your data, start by creating a notification endpoint to a third-party service. After creating notification endpoints, [create notification rules](/influxdb/v2/monitor-alert/notification-rules/create) to send alerts to third-party services on [check statuses](/influxdb/v2/monitor-alert/checks/create).

## Create a notification endpoint

1. In the navigation menu on the left, select **Alerts \> Alerts**.

   Alerts

2. Select **Notification Endpoints**.

3. Click  **Create**.

4. From the **Destination** drop-down list, select a destination endpoint to send notifications to.

5. In the **Name** and **Description** fields, enter a name and description for the endpoint.

6. Enter information to connect to the endpoint:

   * **For HTTP**, enter the **URL** to send the notification.
     Select the **auth method** to use: **None** for no authentication.
     To authenticate with a username and password, select **Basic** and then
     enter credentials in the **Username** and **Password** fields.
     To authenticate with an API token, select **Bearer**, and then enter the
     API token in the **Token** field.

   * **For Slack**, create an [Incoming WebHook](https://api.slack.com/incoming-webhooks#posting_with_webhooks)in Slack, and then enter your webHook URL in the **Slack Incoming WebHook URL** field.

   * **For PagerDuty**:

     * [Create a new service](https://support.pagerduty.com/docs/services-and-integrations#section-create-a-new-service),[add an integration for your service](https://support.pagerduty.com/docs/services-and-integrations#section-add-integrations-to-an-existing-service),
       and then enter the PagerDuty integration key for your new service in the **Routing Key** field.

     * The **Client URL** provides a useful link in your PagerDuty notification.
       Enter any URL that you’d like to use to investigate issues.
       This URL is sent as the `client_url` property in the PagerDuty trigger event.
       By default, the **Client URL** is set to your Monitoring & Alerting History
       page, and the following included in the PagerDuty trigger event:

       ```
       { "client_url": "http://localhost:8086/orgs/<your-org-ID>/alert-history" }
       ```

7. Click **Create Notification Endpoint**.

#### Related

* [Manage checks](/influxdb/v2/monitor-alert/checks/)
* [Manage notification rules](/influxdb/v2/monitor-alert/notification-rules/)