Monitors

Get monitor

Returns a monitor with its full runtime state including evidence buffer.

get/api/v1/monitors/{monitorID}

Request

  • Base URL: https://api.uptimemonitoring.com
  • URL: https://api.uptimemonitoring.com/api/v1/monitors/{monitorID}
  • Auth: HTTP bearer

Path parameters

monitorIDinteger required

Monitor ID.

Response

Monitor with state.

last_check_skippedstring

Populated only on POST /monitors when the create-time initial check did not produce a usable result — either short-circuited before any probe ran, or the probe started but did not finish within the create-time budget, leaving the first check pending. The state row's last_check_at remains null in either case; clients distinguish "no data yet" from "skipped on purpose" via this field.

Vocabulary:

  • domain_rate_limited — the per-domain dispatch cap (DomainLimiter) consumed the slot; the next scheduled tick will retry once the bucket refills.
  • initial_check_timeout — the create-time probe did not return within the server's bounded wait; the monitor is registered normally and the next scheduled tick resolves it.
recipient_idsinteger[]

Attached recipient ids (issue #212). Always present, [] for none. On POST /monitors, reflects any account default recipients attached inside the create transaction — though a monitor born down does not notify them at creation; see Recipient.default.

Example response

{
  "monitor": {
    "name": "Production API",
    "url": "https://api.example.com/health",
    "interval_sec": 60,
    "expected_status": "200",
    "maintenance": {
      "start_time": "23:00",
      "end_time": "03:00",
      "timezone": "Europe/Lisbon"
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.