SolarWinds Pingdom API

Name: Pingdom API
Brand: Pingdom API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMonitoringUptimebearer85 EndpointsREST

For Agents

Create and manage uptime monitoring checks, retrieve performance metrics, configure alerts, and track website availability across multiple global locations.

Install Jentic One Beta

Connect the Pingdom API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pingdom API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Pingdom API.

Create and configure uptime checks for HTTP, HTTPS, TCP, DNS, ICMP, and SMTP protocols

Monitor website performance and page load times from 100+ global test locations

Retrieve detailed check results including response times, status codes, and outage history

GET STARTED

Start building with Pingdom API

Explore with Jentic

View OpenAPI Document

Use for: Create an uptime check for my website that alerts when it goes down, Get the current status of all my monitoring checks, Show me the response time history for example.com over the last 7 days, Set up alerts to notify my Slack channel when a check fails

Not supported: Covers synthetic uptime monitoring and alerting only. Does not include advanced SolarWinds platform features, APM (application performance monitoring), or infrastructure monitoring. Use for website and API endpoint uptime checks.

Jentic publishes the only available OpenAPI specification for Pingdom API, keeping it validated and agent-ready. Pingdom is a website monitoring and uptime tracking service operated by SolarWinds that enables developers to programmatically create and manage uptime checks, retrieve performance data, configure alerts, and generate availability reports. The API exposes comprehensive controls for HTTP, HTTPS, DNS, ICMP, and transaction monitoring checks with multi-region test locations, customizable alert rules, and detailed historical performance metrics. Agents can use Pingdom to automate monitoring setup, integrate uptime data into dashboards, and trigger incident response workflows based on check results.

Use Cases

Patterns agents use Pingdom API for, with concrete tasks.

★ Automated incident detection and alerting

Create uptime checks for critical services and configure multi-channel alerting to notify on-call teams when checks fail. The API enables automated check creation during deployments, integrates with incident management platforms via webhooks, and provides detailed failure context including status codes and response times to accelerate troubleshooting. Maintenance windows can be scheduled programmatically to prevent false alerts during known downtime.

Call POST /checks to create an HTTP check with target URL, check interval, and alert contacts. Configure POST /alerting/contacts and POST /alerting/policies to route notifications. Poll GET /checks/{id} for status and use GET /checks/{id}/results for historical data.

Multi-region performance tracking

Monitor global website performance by creating checks from multiple test locations and aggregating response time data. The API returns per-region performance metrics that reveal geographic latency patterns, CDN effectiveness, and regional availability issues. Teams can build dashboards that compare response times across continents and identify regions requiring infrastructure improvements.

Call GET /checks to list all checks, then GET /checks/{id}/results?includeanalysis=true to retrieve detailed performance data per test location. Aggregate response times by region and render in a dashboard or alert when specific regions exceed thresholds.

SLA compliance reporting and validation

Generate automated uptime and SLA reports for customer-facing services by querying historical check results and calculating availability percentages. The API provides outage timestamps, duration data, and uptime summaries that feed directly into customer dashboards or billing systems. Schedule periodic report generation to track SLA compliance trends and provide evidence for service level agreements.

Call GET /summary.outage/{checkid} to retrieve outage history for a time period, calculate uptime percentage from total time minus outage duration, and generate SLA compliance reports. Use GET /checks/{id}/summary to get pre-calculated uptime metrics.

Agent-driven monitoring through Jentic

Let an agent fulfill a 'monitor my website and alert me if it goes down' request by routing through Jentic. The agent searches for uptime monitoring operations, loads the Pingdom check creation schema, and submits the target URL with alert preferences; Jentic injects the bearer token and returns check status without exposing credentials in the agent context.

Through Jentic, search('create uptime monitoring check'), load Pingdom POST /checks operation, execute with target URL, check type, and interval parameters. Poll GET /checks/{id} via Jentic to retrieve status and alert on failures.

Key Endpoints

85 endpoints — jentic publishes the only available openapi specification for pingdom api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/checks

Create a new uptime or performance monitoring check

GET

/checks

List all monitoring checks in the account

GET

/checks/{checkid}

Get detailed information about a specific check

GET

/checks/{checkid}/results

Retrieve historical check results and performance data

PUT

/checks/{checkid}

Modify an existing monitoring check configuration

DELETE

/checks/{checkid}

Delete a monitoring check

GET

/summary.outage/{checkid}

Get outage history and downtime summary for a check

POST

/maintenance

Create a maintenance window to pause alerting

GET

/alerting/contacts

List all alert notification contacts

POST

/alerting/contacts

Add a new alert notification contact

POST

/checks

Create a new uptime or performance monitoring check

GET

/checks

List all monitoring checks in the account

GET

/checks/{checkid}

Get detailed information about a specific check

GET

/checks/{checkid}/results

Retrieve historical check results and performance data

PUT

/checks/{checkid}

Modify an existing monitoring check configuration

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Pingdom bearer tokens are stored encrypted in the Jentic vault. Jentic applies the Authorization header at execution time so the raw token never enters the agent context, prompt, or trace logs.

Intent-based discovery

Agents search Jentic with intents like 'monitor website uptime' or 'create uptime check' and Jentic returns the Pingdom check creation operation along with parameter schemas, so the agent can set up monitoring without reading documentation.

Time to first call

Direct integration: 3-5 hours to implement authentication, check creation, result polling, and alert configuration. Through Jentic: under 45 minutes to search, load schema, and create first monitoring check with alerts.

FAQs

Specific to using Pingdom API through Jentic.

Why is there no official OpenAPI spec for Pingdom API?

Pingdom does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Pingdom API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Pingdom API use?

The API uses bearer token authentication. Pass your Pingdom API token in the Authorization header as 'Bearer <token>'. Through Jentic, the token is stored encrypted in the vault and applied at execution so it never enters the agent's prompt.

What types of monitoring checks can I create with Pingdom API?

Pingdom supports HTTP/HTTPS, TCP, DNS, ICMP (ping), SMTP, and transaction monitoring (TMS) checks. Each check type monitors different aspects of service availability and can be configured with custom intervals, test locations, and alert thresholds.

How do I configure alerts when a check fails?

Create alert contacts via POST /alerting/contacts with email, SMS, or webhook destinations. Then assign contacts to checks via PUT /checks/{checkid} or configure advanced alert policies with custom escalation rules via the alerting endpoints.

Can I schedule maintenance windows to prevent false alerts?

Yes. Use POST /maintenance to create maintenance windows that temporarily pause alerting for specific checks during planned downtime. Specify start time, duration, and which checks to silence.

How do I get historical uptime data through Jentic?

Install Jentic with pip install jentic, search('get uptime history for a website'), load the Pingdom GET /checks/{checkid}/results operation, and execute with the check ID and time range. Jentic applies your API token automatically.

SolarWinds Pingdom API

Connect the Pingdom API to your agent

Capabilities

Start building with Pingdom API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs