Skip to content

Connect via REST API

Prerequisites

An umk_live_ API key from app.uptimemonitoring.com — see Authentication
curl (any recent version)

Make your first call

List your monitors:

curl https://api.uptimemonitoring.com/api/v1/monitors \
  -H "Authorization: Bearer umk_live_..."

Replace umk_live_... with your actual API key.

Create a monitor

curl -X POST https://api.uptimemonitoring.com/api/v1/monitors \
  -H "Authorization: Bearer umk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "name": "my-api",
    "url": "https://example.com/healthz",
    "type": "http",
    "expected_status": "200"
  }'

See Monitors for the full field reference and response shape.

Verify

A successful list call returns 200 OK with a JSON array. A successful create call returns 200 OK with a {monitor, state} envelope. If you see 401, check the common errors below.

Common errors

Symptom	Cause	Fix
`401 Unauthorized`	Key prefix wrong or key revoked	Confirm the key starts with `umk_live_` — see Authentication
`429 Too Many Requests`	Rate limit exceeded	See Rate Limits
`400` on create	Invalid request body	See Errors — the envelope is `{"error":"<message>"}`, not RFC 7807

Want this through an agent?

Connect UptimeMonitoring to your AI agent instead of calling the REST API directly:

See also

MCP reference and host compatibility matrix
Monitors — full REST API reference
Authentication — key rotation and scopes