Get Uptime Monitor Regions

Retrieve the list of monitoring regions assigned to a specific uptime monitor by providing its monitor_id in the URL path. Each region represents a geographic location from which health checks are performed, allowing teams to track service availability across different parts of the world.

This is especially valuable for identifying location-specific issues, validating global uptime, or optimizing regional infrastructure coverage.

Use cases:

Regional diagnostics — Investigate performance differences or outages limited to certain geographic zones.
Coverage verification — Ensure that a monitor is checking from all required regions based on your application's user base.
Infrastructure planning — Align uptime checks with regional deployments to detect latency or access issues more accurately.

To update region settings, use the appropriate monitor configuration or update endpoint tied to your uptime monitoring service.

Authorization: Bearer YOUR_TOKEN

Path Parameters

id string
The unique resource ID for which regions will be retrieved.
Example: '906a3444-15ce-4410-8041-89a238e9e91f'

JavaScript

Response codes

const axios = require('axios');

const url = 'https://resource-query.api.pinghome.io/v1/resource/906a3444-15ce-4410-8041-89a238e9e91f/regions';

axios.get(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).