# Pingdom

Pingdom is a web performance monitoring service that allows users to monitor the uptime and performance of websites, servers, and applications.

- **Category:** server monitoring
- **Auth:** API_KEY
- **Composio Managed App Available?** N/A
- **Tools:** 13
- **Triggers:** 0
- **Slug:** `PINGDOM`
- **Version:** 20260227_00

## Tools

### Get Pingdom Alert Actions

**Slug:** `PINGDOM_GET_ACTIONS_ALERTS`

Retrieves configured alert actions (notifications) from your Pingdom account. Alert actions define how and where notifications are sent when checks trigger alerts (e.g., email, SMS, webhooks, integrations like Slack/PagerDuty). Use this to list all actions or filter by specific checks, users, delivery channels, or time ranges. Supports pagination for large result sets.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `via` | array | No | List of notification delivery channels to filter by. Tested values: 'email', 'sms'. Note: Other integration types may not be supported by this filter parameter. |
| `limit` | integer | No | Maximum number of alert actions to return per request. Valid range: 1-100. |
| `start` | integer | No | Starting index for pagination (offset). Use with limit for paginating through results. |
| `endtime` | integer | No | Filter actions created/triggered before this Unix timestamp (in seconds). Use with starttime for time-range queries. |
| `userids` | array | No | List of user IDs to filter actions. Only returns actions created by or assigned to these specific users. |
| `checkids` | array | No | List of check IDs to filter actions. Only returns actions associated with these specific uptime/transaction checks. |
| `starttime` | integer | No | Filter actions created/triggered after this Unix timestamp (in seconds). Use for time-range queries. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Checks List

**Slug:** `PINGDOM_GET_CHECKS_LIST`

Retrieves a list of all uptime/monitoring checks configured in Pingdom with optional filtering and pagination. Use this to: view all monitoring checks, filter by status/type/tags, search by name, or paginate through large check lists. Returns check details including ID, name, hostname, status, type, resolution, and optional tags.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No | Filter checks by name (partial match allowed) |
| `tags` | string | No | Comma-separated list of tags to filter checks |
| `team` | integer | No | Filter checks by team ID |
| `type` | string | No | Type of check to filter (e.g., http, tcp, udp) |
| `limit` | integer | No | Maximum number of checks to return (1-250) |
| `offset` | integer | No | Index of the first check to return for pagination (zero-based) |
| `status` | string | No | Filter checks by status (up, down, paused) |
| `probeids` | string | No | Comma-separated list of probe IDs for filtering checks |
| `transaction` | boolean | No | If true, only return transaction checks |
| `include_tags` | boolean | No | If true, include tag details with each check |
| `integrationids` | string | No | Comma-separated list of integration IDs for filtering |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Contact Details

**Slug:** `PINGDOM_GET_CONTACT_DETAILS`

Retrieves comprehensive details of a specific Pingdom alerting contact by ID, including all configured notification methods (email, SMS), team memberships, contact type, and pause status. Use this when you need complete information about a contact's notification configuration.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `contactid` | integer | Yes | Unique identifier of the alerting contact to retrieve |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Contacts

**Slug:** `PINGDOM_GET_CONTACTS`

Tool to retrieve all alerting contacts. Use when you need to list every contact along with their notification targets after establishing a Pingdom session.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Credits

**Slug:** `PINGDOM_GET_CREDITS`

Retrieves comprehensive account information including check limits, SMS credits, and resource usage. Use this to monitor available checks (uptime and transaction), SMS credits, RUM sites, and alerting user capacity. Returns current usage counts and available slots for all resource types.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Maintenance Occurrences

**Slug:** `PINGDOM_GET_LIST_MAINTENANCE_OCCURRENCES`

Tool to list maintenance occurrences. Use when you need occurrences filtered by time range or a specific maintenance window ID.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | Maximum number of occurrences to return |
| `offset` | integer | No | Start listing from this occurrence offset |
| `to_time` | integer | No | Unix timestamp marking the end of the time range for occurrences |
| `from_time` | integer | No | Unix timestamp marking the start of the time range to retrieve occurrences |
| `maintenancewindowid` | integer | No | Filter occurrences by a specific maintenance window ID |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Maintenance Windows

**Slug:** `PINGDOM_GET_MAINTENANCE_WINDOWS`

Tool to retrieve a list of maintenance windows. Use when you need to list user's maintenance windows with optional pagination and time range filters.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | Number of maintenance windows per page (1-1000) |
| `offset` | integer | No | Offset for pagination (zero-based) |
| `to_time` | integer | No | Only maintenance windows starting before this Unix timestamp |
| `from_time` | integer | No | Only maintenance windows starting after this Unix timestamp |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Probes

**Slug:** `PINGDOM_GET_PROBES`

Retrieves the complete list of Pingdom probe servers worldwide. This action returns all available probe servers that can be used for monitoring checks. Probes are distributed globally across regions (NA, EU, APAC, LATAM) and provide information about their location, IP addresses (IPv4 and IPv6), and availability status. Use this when you need to: - List all available monitoring locations - Select probes for creating uptime or transaction checks - Identify probe servers by region or country - Get IP addresses of probe servers for allowlisting

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Reference Data

**Slug:** `PINGDOM_GET_REFERENCE_DATA`

Retrieves Pingdom reference data including regions, timezones, datetime formats, number formats, and countries. This data is used for configuring Pingdom account settings, checks, and understanding available formatting options. Use this when you need to know valid timezone IDs, region configurations, or country codes for Pingdom operations.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Single Check

**Slug:** `PINGDOM_GET_SINGLE_CHECK`

Perform a single on-demand Pingdom check against a target host. This executes an immediate test from a specified probe (or random probe if not specified) and returns the result. Use this when you need a quick connectivity or performance test of a website, server, or service. Example uses: "Test if google.com is reachable", "Check response time for example.com from a specific region", "Verify HTTP status of api.mysite.com".

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `url` | string | No | Full URL path for HTTP checks (e.g., '/status') |
| `host` | string | Yes | Hostname or IP address to test |
| `port` | integer | No | Port number for tcp/udp checks (1-65535) |
| `type` | string ("ping" | "http" | "tcp" | "udp" | "dns") | Yes | Type of check to perform |
| `probeid` | integer | No | Pingdom probe ID to execute the check from. If not specified, a random probe will be used |
| `expectedip` | string | No | Expected IP address for DNS checks. Required when type is 'dns' |
| `stringtosend` | string | No | String to send to the server for TCP/UDP checks. Required for UDP checks |
| `stringtoexpect` | string | No | String to expect in response for TCP/UDP checks |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Team Details

**Slug:** `PINGDOM_GET_TEAM_DETAILS`

Tool to fetch detailed information for a specific alerting team. Use after listing teams to get full members and integrations details.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `teamid` | integer | Yes | Unique identifier of the Pingdom alerting team |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Teams

**Slug:** `PINGDOM_GET_TEAMS`

Tool to retrieve all alerting teams and their members. Use after authenticating to Pingdom to manage team configurations.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get TMS Transaction Checks List

**Slug:** `PINGDOM_GET_TMS_TRANSACTION_CHECKS_LIST`

Retrieves a paginated list of all transaction (TMS) checks configured in Pingdom. Transaction checks (also called TMS checks) are synthetic monitoring tests that simulate user interactions with web applications by executing scripted sequences of actions. Use this action to: - Get an overview of all configured transaction checks - Retrieve check IDs, names, types, and current status - Paginate through large lists of transaction checks Returns an empty list if no transaction checks are configured.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | Maximum number of transaction checks to return per page (1-1000). Defaults to 1000 if not specified. |
| `offset` | integer | No | Zero-based index to start returning transaction checks from. Use with limit for pagination (e.g., offset=0 for first page, offset=100 for second page with limit=100). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |