Delete Multiple Uptime Monitors

Efficiently remove multiple uptime monitors in one operation by passing their ids as a query parameter array. This bulk deletion feature is ideal for large-scale cleanup tasks, such as retiring services, restructuring environments, or clearing out test monitors after staging deployments.

Instead of making individual delete requests for each monitor, this endpoint allows you to streamline operations by submitting a list of monitor IDs in a single call — saving time and reducing API overhead.

Common use cases include:
  • Service decommissioning — Remove all monitors associated with a shutdown system or deprecated feature set.
  • Bulk cleanup — Delete outdated, duplicated, or test monitors during infrastructure reorganization.
  • Workspace resets — Prepare clean environments by clearing monitors in bulk between testing or onboarding phases.

To fetch monitor IDs before deletion, use the Get Uptime Monitors endpoint.

Authorization: Bearer YOUR_TOKEN



Expected Behavior:

  • On success, the specified uptime monitoring resources will be deleted, and a confirmation message will be returned.
  • If the request is unauthorized or the IDs are invalid, an appropriate error message will be returned.
Query Parameters
  • id string
    A list of resource IDs to delete.
    Example: ['6766163a-568d-47b4-a1fa-91a0957e06d4', 'c03b02ec-244f-4d2c-8f68-3910071ed5c8']
JavaScript
Response codes
const axios = require('axios');

const url = "https://resource-cmd.api.pinghome.io/v1/resource?id=6766163a-568d-47b4-a1fa-91a0957e06d4&id=c03b02ec-244f-4d2c-8f68-3910071ed5c8";

axios.delete(url, {
    headers: {
        'Authorization': 'Bearer YOUR_TOKEN'
    }
})
.then(response => {
    console.log(response.data);
})
.catch(error => {
    console.error(error);
});
ResponseThis section is used to view the possible HTTP response codes returned by the API. These codes indicate the status of a request, such as 201 (Created), 401 (Unauthorized), 409 (Conflict), or 422 (Unprocessable Entity).