---
title: "Changes to Get a monitor by id"
method: GET
path: "/monitors/{monitorId}"
---

# Changes to Get a monitor by id

`GET /monitors/{monitorId}`

> Every recorded change to this endpoint, newest first.

## Timeline

Changed in 9 of 38 revisions.

- **2026-08-28** `a9ac59e12c59` — 1 info
- **2026-08-25** `1f334de2d559` — 2 info
- **2026-06-24** `648dc5ab4761` — 2 info
- **2026-06-09** `ca827e5b975f` — 1 info
- **2026-05-27** `dd1708803c7c` — 1 info
- **2026-05-11** `59d86e7d3831` — 1 warning, 2 info
- **2026-05-01** `39082d385dda` — 2 breaking, 2 warning, 8 info
- **2025-08-11** `db719f9e3d34` — 1 breaking, 3 warning, 7 info
- **2025-04-20** `b97ec6888b3c` — 32 breaking, 13 warning, 8 info

## Changes

- **2026-08-28** `a9ac59e12c59` — 1 info
  - added the optional property `data/sshPrivateKey` to the response with the `200` status
- **2026-08-25** `1f334de2d559` — 2 info
  - added the optional property `data/proxyId` to the response with the `200` status
  - added the required property `data/proxyMode` to the response with the `200` status
- **2026-06-24** `648dc5ab4761` — 2 info
  - added the required property `data/lastEvaluatedAt` to the response with the `200` status
  - added the required property `data/method` to the response with the `200` status
- **2026-06-09** `ca827e5b975f` — 1 info
  - added the optional property `data/customUpCodes` to the response with the `200` status
- **2026-05-27** `dd1708803c7c` — 1 info
  - added the required property `data/tags` to the response with the `200` status
- **2026-05-11** `59d86e7d3831` — 1 warning, 2 info
  - added the new `dns` enum value to the `data/type` response property for the response status `200`
  - added the optional property `data/dnsRecordType` to the response with the `200` status
  - added the optional property `data/dnsServer` to the response with the `200` status
- **2026-05-01** `39082d385dda` — 2 breaking, 2 warning, 8 info
  - for the `path` request parameter `monitorId`, the minLength was increased from `0` to `1`
  - the response's body type/format changed from ``/`` to `object`/`` for status `200`
  - removed the optional property `details` from the response with the `500` status
  - added the new `false` enum value to the `success` response property for the response status `500`
  - removed `#/components/schemas/SuccessResponse, subschema #2` from the response body `allOf` list for the response status `200`
  - added the non-success response with the status `401`
  - added the non-success response with the status `403`
  - removed the non-success response with the status `404`
  - added the optional property `data` to the response with the `500` status
  - added the required property `data` to the response with the `200` status
  - added the required property `msg` to the response with the `200` status
  - added the required property `success` to the response with the `200` status
- **2025-08-11** `db719f9e3d34` — 1 breaking, 3 warning, 7 info
  - the response's body type/format changed from `object`/`` to ``/`` for status `200`
  - removed the optional property `data` from the response with the `200` status
  - removed the optional property `msg` from the response with the `200` status
  - removed the optional property `success` from the response with the `200` status
  - added `#/components/schemas/SuccessResponse, subschema #2` to the response body `allOf` list for the response status `200`
  - added the non-success response with the status `404`
  - removed the non-success response with the status `422`
  - added the optional property `details` to the response with the `500` status
  - the response property `msg` became required for the status `500`
  - the response property `success` became required for the status `500`
  - the `success` response's property default value `false` was removed for the status `500`
- **2025-04-20** `b97ec6888b3c` — 32 breaking, 13 warning, 8 info
  - the response property `data` became optional for the status `200`
  - the response property `msg` became optional for the status `200`
  - the response property `msg` became optional for the status `500`
  - the response property `success` became optional for the status `200`
  - the response property `success` became optional for the status `500`
  - removed the required property `data/_id` from the response with the `200` status
  - removed the required property `data/cpuAlertThreshold` from the response with the `200` status
  - removed the required property `data/createdAt` from the response with the `200` status
  - removed the required property `data/diskAlertThreshold` from the response with the `200` status
  - removed the required property `data/geoCheckEnabled` from the response with the `200` status
  - removed the required property `data/geoCheckInterval` from the response with the `200` status
  - removed the required property `data/geoCheckLocations` from the response with the `200` status
  - removed the required property `data/ignoreTlsErrors` from the response with the `200` status
  - removed the required property `data/interval` from the response with the `200` status
  - removed the required property `data/isActive` from the response with the `200` status
  - removed the required property `data/lastEvaluatedAt` from the response with the `200` status
  - removed the required property `data/memoryAlertThreshold` from the response with the `200` status
  - removed the required property `data/method` from the response with the `200` status
  - removed the required property `data/name` from the response with the `200` status
  - removed the required property `data/notifications` from the response with the `200` status
  - removed the required property `data/selectedDisks` from the response with the `200` status
  - removed the required property `data/status` from the response with the `200` status
  - removed the required property `data/statusWindowSize` from the response with the `200` status
  - removed the required property `data/statusWindowThreshold` from the response with the `200` status
  - removed the required property `data/tags` from the response with the `200` status
  - removed the required property `data/teamId` from the response with the `200` status
  - removed the required property `data/tempAlertThreshold` from the response with the `200` status
  - removed the required property `data/type` from the response with the `200` status
  - removed the required property `data/updatedAt` from the response with the `200` status
  - removed the required property `data/url` from the response with the `200` status
  - removed the required property `data/useAdvancedMatching` from the response with the `200` status
  - removed the required property `data/userId` from the response with the `200` status
  - removed the optional property `data` from the response with the `500` status
  - removed the optional property `data/customUpCodes` from the response with the `200` status
  - removed the optional property `data/description` from the response with the `200` status
  - removed the optional property `data/dnsRecordType` from the response with the `200` status
  - removed the optional property `data/dnsServer` from the response with the `200` status
  - removed the optional property `data/expectedValue` from the response with the `200` status
  - removed the optional property `data/gameId` from the response with the `200` status
  - removed the optional property `data/group` from the response with the `200` status
  - …13 more

---

[Operation](https://skmtc.dev/bluewave-labs/apis/checkmate-api/docs/monitors/:monitorId/get.md) · [API](https://skmtc.dev/bluewave-labs/apis/checkmate-api.md) · [Page](https://skmtc.dev/bluewave-labs/apis/checkmate-api/changes/monitors/:monitorId/get)
