Authenticate with a Bearer token: generate an API token in My Pingdom under API > Token, then include Authorization: Bearer YOUR_TOKEN in all request headers
List existing uptime checks: GET https://api.pingdom.com/api/3.1/checks to retrieve all checks with their IDs, status, and type
Create a new HTTP uptime check: POST https://api.pingdom.com/api/3.1/checks with body parameters including name, host, type (http), resolution (check interval in minutes), and contactids (comma-separated contact list IDs)
List transaction checks: GET https://api.pingdom.com/api/3.1/tm/checks to retrieve transaction monitoring checks; transaction checks are managed under the /tm/ path prefix
Retrieve uptime/latency summaries: GET https://api.pingdom.com/api/3.1/summary.average/{checkid} with from and to Unix timestamp parameters
Pause a check for maintenance: PUT https://api.pingdom.com/api/3.1/checks/{checkid} with paused=true in the request body
Known gotchas
Transaction checks (multi-step browser recordings) are managed under the /tm/ path and have a separate check creation interface; they cannot be fully created via the API — recordings must be created in the Pingdom UI
Contact list IDs must be retrieved separately via GET /api/3.1/contacts before creating checks that reference them; supplying non-existent IDs silently drops the alerting association
The Pingdom API is owned by SolarWinds; rate limits and authentication requirements are documented at docs.pingdom.com — verify current limits before bulk operations
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp