Monitors API

Read the monitors in your team and pull their recent check history. Use these endpoints to build dashboards, export uptime data, or feed monitor status into your own tooling. Everything here is read-only — creating and editing monitors stays in the dashboard: open Monitors in Servor.

These endpoints require the monitors:read scope.

curl https://api.servor.app/v1/monitors \
  -H "Authorization: Bearer sv_live_..."

[
  {
    "id": "uuid",
    "name": "Homepage",
    "type": "http",
    "status": "up",
    "enabled": true,
    "intervalSeconds": 60,
    "lastCheckAt": "2026-08-20T10:00:00.000Z",
    "lastStatusChangeAt": null
  }
]

curl https://api.servor.app/v1/monitors/:id/checks \
  -H "Authorization: Bearer sv_live_..."

[
  {
    "status": "up",
    "latencyMs": 138,
    "checkedAt": "2026-08-20T10:00:00.000Z"
  }
]

What you get back

• GET /v1/monitors — the list of monitors in your team, each with its type, target, current status (up, degraded or down) and uptime percentage.
• GET /v1/monitors/{id}/checks — the recent checks for one monitor, so you can plot response times or reconstruct a timeline.

Monitor types include HTTP, TCP/port, ping, DNS, SSL certificate and keyword checks. See monitor types for what each one measures and monitor status for how up / degraded / down are decided.

Example

curl https://api.servor.app/v1/monitors \
  -H "Authorization: Bearer sv_live_..."

To read one monitor's check history, take an id from that list:

curl https://api.servor.app/v1/monitors/mon_123/checks \
  -H "Authorization: Bearer sv_live_..."

Notes

• CPU, RAM and disk figures are resource metrics reported by the server agent, not part of the monitor check payload.
• A 403 means your token is missing the monitors:read scope — see errors for the full list of status codes.

See also