Change Uptime Monitor Status

Toggle the operational status of an existing uptime monitor by enabling or disabling it as needed. This endpoint gives teams fine-grained control over monitoring activity — allowing them to pause or resume checks without permanently deleting the monitor.

To update the status, include the monitor_id in the path and provide the enabled flag in the request body, set to true to activate the monitor or false to deactivate it.

When to use this:
  • Scheduled maintenance — Temporarily disable monitoring to avoid false-positive alerts during planned downtimes.
  • Service deactivation — Pause monitoring for services that are temporarily offline or in standby mode.
  • Reactivation — Re-enable monitors once the related service is stable and ready to be tracked again.

This functionality is useful for reducing alert noise, maintaining clean uptime logs, and ensuring accurate incident tracking without losing historical data tied to the monitor.

Authorization: Bearer YOUR_TOKEN



Expected Behavior:

  • On success, the status of the uptime resource will be updated, 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 whose status is being updated.
    Example: 'c03b02ec-244f-4d2c-8f68-3910071ed5c8'
Request Body Parameters
  • enabled boolean
    A boolean value that determines the status of the uptime monitoring resource. Set to true to enable the resource or false to disable it.
    Example: true
JavaScript
Response codes
const axios = require('axios');

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

axios.put(url, data, {
    headers: {
        'Authorization': 'Bearer YOUR_TOKEN',
        'Content-Type': 'application/json'
    }
})
.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).