Delete Uptime Monitor
Permanently remove a specific uptime monitor by providing its monitor_id in the request path. Once deleted, the monitor will no longer perform health checks, collect availability data, or trigger alerts for the associated service.

This endpoint is useful when a monitored service has been retired, replaced, or is no longer relevant to your team’s operational needs. It ensures your monitoring environment remains clean and focused only on active, meaningful targets.

Key scenarios:
  • Service decommissioning — Remove monitors tied to systems that are permanently shut down.
  • Monitor cleanup — Eliminate unused or outdated monitors to simplify your workspace and reduce visual clutter.
  • Avoid unnecessary alerts — Prevent alerts from triggering on endpoints that are intentionally offline or out of scope.

Note: This action is irreversible. To temporarily pause a monitor instead, consider using the Change Uptime Monitor Status endpoint.

Authorization: Bearer YOUR_TOKEN



Expected Behavior:

  • On success, the specified uptime resource will be deleted, and a confirmation message will be returned.
  • If the request is unauthorized or the provided ID is invalid, an error message will be returned specifying the issue.
Path Parameters
  • id string
    The unique ID of the uptime resource to be deleted.
    Example: 'c03b02ec-244f-4d2c-8f68-3910071ed5c8'
JavaScript
Response codes
const axios = require('axios');

const url = 'https://resource-cmd.api.pinghome.io/v1/resource/c03b02ec-244f-4d2c-8f68-3910071ed5c8';

axios.delete(url, {
    headers: {
        'Authorization': 'Bearer YOUR_TOKEN'
    }
})
.then(response => {
    console.log('Resource deleted successfully');
})
.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).