> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Pingdom as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/pingdom

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Creating a Pingdom API token](#creating-a-pingdom-api-token)
- [Linking Pingdom](#linking-pingdom)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Sync modes](#sync-modes)
- [Available datasets and endpoints](#available-datasets-and-endpoints)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Pingdom connector syncs your uptime monitoring data into PostHog, including checks, probes, maintenance windows, and alerts.

## Creating a Pingdom API token

Pingdom uses Bearer token authentication. A read-only token is sufficient for syncing data into PostHog.

1.  Log in to [My Pingdom](https://my.pingdom.com/app/api-tokens).
2.  Go to **Settings** > **Pingdom API**.
3.  Click **Add API token**, give it a name, and select read access.
4.  Copy the token.

For more details, see [Pingdom's API documentation](https://docs.pingdom.com/api/).

## Linking Pingdom

1.  Go to the [Data pipeline sources page](https://app.posthog.com/data-management/sources) in PostHog.
2.  Click **\+ New source** and then click **Link** next to Pingdom.
3.  Paste your Pingdom **API token**.
4.  Click **Next**, choose the tables you want to sync, and then click **Import**.

Once the sync completes, you can query your Pingdom data directly in PostHog.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API token` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `checks` | An uptime check that monitors the availability of a host or service from Pingdom. | Full refresh | — | — |
| `probes` | A Pingdom probe server that runs checks from a specific geographic location. | Full refresh | — | — |
| `maintenance` | A scheduled maintenance window during which checks are paused. | Full refresh | — | — |
| `alerts` | An alert action triggered by a check state change, such as a notification sent to a user. | Incremental, Full refresh | time | — |

## Sync modes

Pingdom tables use different sync strategies depending on whether the Pingdom API supports filtering by time:

-   **Full refresh** - The `checks`, `probes`, and `maintenance` tables are re-downloaded on every sync. These are small dimension tables and the Pingdom API doesn't expose an "updated since" filter for them.
-   **Incremental** - The `alerts` table supports incremental syncing. PostHog uses the `from` UNIX timestamp filter on the `/actions` endpoint to only fetch alerts newer than the last sync.

## Available datasets and endpoints

| Dataset | Endpoint path | Sync mode | Primary key |
| --- | --- | --- | --- |
| `checks` | `/checks` | Full refresh | `id` |
| `probes` | `/probes` | Full refresh | `id` |
| `maintenance` | `/maintenance` | Full refresh | `id` |
| `alerts` | `/actions` | Incremental | `checkid`, `time`, `userid`, `via` |

All endpoints use the Pingdom API 3.1 (`api.pingdom.com/api/3.1`).

The `alerts` table uses a composite primary key because individual alert rows don't have a unique identifier. Duplicate rows with the same key combination are tolerated by the pipeline.