Alerts

Custom endpoint checks

Saved URL checks that poll a specific page or API on a schedule with their own run history, plus the one-off probe. Limits: 30 checks, 60 probe runs an hour.

Updated · 2 min read

The uptime probe watches a domain's root. A custom endpoint check watches a specific URL: a login page, a health endpoint, a checkout, a client's staging site.

Where

  • Web: Monitor, Custom checks.
  • API/MCP: GET/POST /api/status/custom-checks, PATCH/DELETE /api/status/custom-checks/:id, POST …/:id/run, GET …/:id/runs; tools list_status_checks, create_status_check, run_status_check, delete_status_check.

The iOS app reads these through the web dashboard (Account, More tools).

What a check is

A name (up to 100 characters) and a public HTTPS or HTTP URL. Optionally a method, headers and a small body (16 KB) for an API endpoint. Each run records whether the target responded, the status, timing, and up to 256 KB of the body plus every response header, so a failing check shows you what the endpoint actually said.

Redirects are followed, and every hop is checked against the public-network rule: private addresses, loopback and link-local targets are refused, so a check cannot be pointed at something inside our network or yours.

Limits

Limit Value
Saved checks per account 30
Outbound probe runs per account per hour 60, counted across saved checks and one-off probes; a refusal says how many minutes until the hour resets
Runs returned per check Up to 40

The one-off probe

POST /api/status/custom-probe sends a request you compose (method, headers, body) to a host from our network and returns the response without saving anything. Because it is a general-purpose fetch from our egress, it needs a paid plan (the scheduled_monitoring capability, Starter and up) and proven ownership of the target. Saved checks can be created on any plan.

Common questions

Does a failing check alert me? A saved check records its result and shows red in the list; it does not currently send a push or email on its own. Use the domain uptime probe for alerting on the root, and read the check's run history for the endpoint.

Can I check a page behind a login? Only if the login is a header (an API key or bearer token). Cookie-based sessions are not supported.

Still stuck?

Ask the people who run the scanner.

Send the domain and what you expected to see. We look at the same scan you are looking at and write back with what it means and what to change.