Developer surface

PulseTrace + REST API

Everything the dashboard does, as JSON.

Monitors, incidents, checks, intelligence events, reports and status pages are all available over a versioned REST API with scoped API keys, service accounts, per-key rate limits and environment restrictions.

Set it up in three steps

1Settings → Developer & API → API Keys → create a key. Choose scopes (e.g. monitors:read, monitors:write), environments and an expiry; the key is shown once.
2Call https://api.pulsetrace.app/api/v1/… with Authorization: Bearer pt_live_…. Every response carries a request id and a consistent error envelope.
3Watch usage under API Usage, and rotate or revoke keys without downtime.

Start monitoring free Read the docs

curl

curl -s https://api.pulsetrace.app/api/v1/monitors \
  -H "Authorization: Bearer pt_live_4f2a…" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Checkout API",
    "type": "http",
    "target": "https://api.example.com/health",
    "interval_seconds": 60,
    "region_codes": ["us-east", "eu-west"],
    "config": { "assertions": [{ "type": "status", "equals": 200 }] }
  }'

Questions about REST API

Are there rate limits?

Yes, per key, with separate read/write/delete budgets you can set when creating the key; limits are returned in response headers.

Is there an OpenAPI spec?

Yes — the API documentation page links the spec, and the same spec powers monitor import.

More developer surfaces

MCP serverLet Claude, Cursor and your own agents run your monitoring.OpenAPI importTurn a spec into a monitor per endpoint.Probe agentCheck from inside your own network.