Skip to content

Read one DNS record monitor.

GET
/dns/record-monitor/{monitor_id}
curl --request GET \
--url https://api.siteqwality.com/dns/record-monitor/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \
--header 'Authorization: Bearer <token>'
monitor_id
required
string format: uuid

DNS monitor identifier

The DNS monitor

Media type application/json

A DNS record monitor as the api returns it.

object
id
required
string format: uuid
account_id
required
string format: uuid
http_job_id
string | null format: uuid
created_at
required
string format: date-time
friendly_name
string | null
domain
required
string
watched
required
Array<object>
object
interval_seconds
required
integer format: int32
paused
required
boolean
current_status
required

pending | baselined | changed | unreachable.

Deliberately never success: a monitor that has never run says so instead of claiming to be fine.

string
last_run_at
string | null format: date-time
last_status_change_at
string | null format: date-time
last_failure_reason

When set, everything displayed for this monitor is LAST KNOWN, not current: a failed check keeps the previous values rather than nulling them, so this field is what makes the staleness legible.

string | null
last_failure_at
string | null format: date-time
group_notification_ids
required
Array<string>
Example generated
{
"id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
"account_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
"http_job_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
"created_at": "2026-04-15T12:00:00Z",
"friendly_name": "example",
"domain": "example",
"watched": [
{}
],
"interval_seconds": 1,
"paused": true,
"current_status": "example",
"last_run_at": "2026-04-15T12:00:00Z",
"last_status_change_at": "2026-04-15T12:00:00Z",
"last_failure_reason": "example",
"last_failure_at": "2026-04-15T12:00:00Z",
"group_notification_ids": [
"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0"
]
}

Missing or invalid authentication

DNS monitor not found

Internal server error