Pingdom

Pingdom is a website and API uptime and performance monitoring service with real-time alerting. The Pingdom REST API (version 3.1) provides programmatic access to uptime checks, raw and summarized performance results, root cause analysis, alert history, contacts, maintenance windows, and email report subscriptions. Nexla connects to the Pingdom API so you can ingest monitoring data for analysis and reporting, or manage Pingdom resources from your data flows.

Power end-to-end data operations for your Pingdom API with Nexla. Our bi-directional Pingdom connector is purpose-built for Pingdom, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Pingdom or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Pingdom workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Pingdom credential, you need an API token from your Pingdom account. Pingdom API 3.1 uses Bearer token authentication: the token is sent in the Authorization header as Authorization: Bearer {token} with each request. API tokens are account-scoped and carry the permissions of the user who generated them, so create the token with an access level appropriate for your use case.

To generate a Pingdom API token, follow these steps:

1. Sign in to your Pingdom account.

2. Click Integrations in the left-side menu, then select The Pingdom API.

3. Click Add API token.

4. Enter a name for the token and choose the access level (for example, read-only if you only need to ingest monitoring data, or read/write if you plan to manage checks, contacts, or maintenance windows from Nexla).

5. Click Generate token.

6. Copy the generated API token and store it securely. Treat the token as a secret, as it grants access to your Pingdom account data based on the access level you selected. If a token is compromised, revoke it in the same The Pingdom API settings screen and generate a new one.

For more information about authentication and available resources, see the Pingdom Public API documentation.

Authenticate

Credentials required

An authentication method that requires sending a unique secret token with each API request

Field	Required	Secret	Description
API Key Value	Yes	Yes	An encoded string value used as a secret token to authenticate API requests

Enter only the raw API token in the API Key Value field. Nexla automatically sends it in the Authorization header as Authorization: Bearer <your token> for every request.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Pingdom API token in the API Key Value field. This is the token you generated in Prerequisites.

   The API token is sent as a Bearer token in the Authorization header for all requests to the Pingdom API. Keep it confidential. If the token is compromised, revoke it in your Pingdom account and generate a new one.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Pingdom connector tile, then select the credential that will be used to connect to Pingdom, and click Next; or, create a new Pingdom credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Pingdom endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List all checks

Retrieves the list of uptime checks in your Pingdom account.

• Optional query parameters let you page through results with Limit and Offset, and filter by Tags and Include Tags.

[Rest API] Get detailed information for a check

Retrieves the full configuration and current state for a single check.

• Provide the target check in the Checkid parameter.

[Rest API] Get raw check results

Retrieves the raw, individual test results for a check.

• Provide the Checkid, and optionally narrow the results with the From, To, Limit, Probes, and Status parameters.

[Rest API] Get average uptime/response time for a check

Retrieves the average uptime and response time for a check over a time range.

• Provide the Checkid, and optionally bound the range with the From and To parameters.

[Rest API] Get response time averages by hour of day

Retrieves response time averages for a check broken down by hour of the day.

• Provide the Checkid, and optionally bound the range with the From and To parameters.

[Rest API] Get status change summary for a check

Retrieves the list of status changes (outages) for a check over a time range.

• Provide the Checkid, and optionally bound and sort the results with the From, To, and Order parameters.

[Rest API] Get performance summary for a check

Retrieves a performance summary for a check, aggregated over a time range.

• Provide the Checkid, and optionally set the From, To, and Resolution parameters to control the aggregation window and granularity.

[Rest API] List root cause analysis results for a check

Retrieves the list of root cause analysis results generated for a check.

• Provide the Checkid, and optionally page through results with the Limit and Offset parameters.

[Rest API] Get raw root cause analysis data

Retrieves the raw data for a specific root cause analysis result.

• Provide the Checkid and the Analysisid identifying the analysis result to fetch.

[Rest API] List alerts that have been generated

Retrieves the history of alerts (actions) that Pingdom has generated.

• Optional parameters let you page and filter the results: From, To, Limit, Offset, Checkids, Contactids, and Status.

[Rest API] List alert contacts

Retrieves the list of alert contacts configured in your Pingdom account.

• Optional Limit and Offset parameters page through the results.

[Rest API] Get a specific contact

Retrieves a single alert contact by identifier.

• Provide the target contact in the Contactid parameter.

[Rest API] List maintenance windows

Retrieves the list of scheduled maintenance windows.

• Optional From and To parameters bound the time range of returned windows.

[Rest API] Get a specific maintenance window

Retrieves a single maintenance window by identifier.

• Provide the target window in the Maintenanceid parameter.

[Rest API] List subscribed email reports

Retrieves the list of email report subscriptions in your account.

• This endpoint takes no additional parameters.

[Rest API] Create a new email report subscription

Creates a new email report subscription and returns the API response.

• This endpoint issues a POST request to create the subscription; the response is captured as source data.

[Rest API] Update an email report subscription

Updates an existing email report subscription and returns the API response.

• Provide the Reportid identifying the subscription to update; the response is captured as source data.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Pingdom data sources can also be manually configured to ingest data from any valid Pingdom API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Pingdom data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Pingdom destination, and select the Send to Destination option from the menu. Select the Pingdom connector from the list of available destination connectors, then select the credential that will be used to connect to Pingdom, and click Next; or, create a new Pingdom credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Pingdom endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create a new check

Creates a new uptime check in Pingdom from records in a Nexset.

• Each record is sent as a JSON request body to create a check. The record should contain the check properties expected by the Pingdom API.

[Rest API] Pause or change resolution for multiple checks

Pauses or changes the check resolution for multiple checks in a single request.

• Each record is sent as a JSON request body specifying the checks to modify and the new settings to apply.

[Rest API] Delete multiple checks

Deletes multiple checks in a single request.

• Each record is sent as a JSON request body identifying the checks to delete. This operation is irreversible.

[Rest API] Update a check

Updates the configuration of a single check.

• Provide the target check in the Checkid parameter. Each record is sent as a JSON request body containing the fields to update.

[Rest API] Delete a check

Deletes a single check.

• Provide the target check in the Checkid parameter. This operation is irreversible.

[Rest API] Create a new contact

Creates a new alert contact in Pingdom from records in a Nexset.

• Each record is sent as a JSON request body containing the contact properties expected by the Pingdom API.

[Rest API] Update a contact

Updates an existing alert contact.

• Provide the target contact in the Contactid parameter. Each record is sent as a JSON request body containing the fields to update.

[Rest API] Delete a contact

Deletes a single alert contact.

• Provide the target contact in the Contactid parameter. This operation is irreversible.

[Rest API] Create a new maintenance window

Creates a new maintenance window in Pingdom from records in a Nexset.

• Each record is sent as a JSON request body containing the maintenance window properties expected by the Pingdom API.

[Rest API] Delete multiple maintenance windows

Deletes multiple maintenance windows in a single request.

• Each record is sent as a JSON request body identifying the maintenance windows to delete. This operation is irreversible.

[Rest API] Update a maintenance window

Updates an existing maintenance window.

• Provide the target window in the Maintenanceid parameter. Each record is sent as a JSON request body containing the fields to update.

[Rest API] Delete a maintenance window

Deletes a single maintenance window.

• Provide the target window in the Maintenanceid parameter. This operation is irreversible.

[Rest API] Delete an email report subscription

Deletes an existing email report subscription.

• Provide the target subscription in the Reportid parameter. This operation is irreversible.

Manual configuration

Pingdom destinations can also be manually configured to send data to any valid Pingdom API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Pingdom write endpoints expect JSON request bodies. For update and delete operations that target a single resource, include the resource identifier (for example, the check, contact, maintenance window, or report ID) in the endpoint parameter so the request is routed to the correct object.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Pingdom endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Pingdom endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.