HTTP checks

An HTTP check sends a request to a URL on a schedule, asserts on the response, and notifies you when something is wrong. They’re the most common kind of monitor — start here if you’re checking that a website, API, or webhook endpoint is up.

When to use HTTP checks

• A website or web app you want kept online.
• A REST or GraphQL API you publish to customers.
• A webhook receiver that needs to be reachable.
• Internal services with public health endpoints.

For ping-style “is the box up” checks where there’s no HTTP server, use a DNS check on the hostname or a cron heartbeat the box pings.

How it works

Every HTTP check has a schedule (default: every 10 minutes; minimum 30 seconds on paid plans) and a target URL. On each tick:

1. SiteQwality issues the configured HTTP request from one or more regions (us-east-1 by default; multi-region requires a paid plan).
2. The response is evaluated against your assertions: status code, response body keyword search, response time.
3. If the result differs from the previous status (e.g., success → failure), an incident opens and your notification rules fire.
4. The result is recorded for uptime/latency dashboards and historical reporting.

A single HTTP check can also automatically provision a paired:

• TLS check — tracks the certificate’s expiry and chain.
• DNS check — tracks the registrable domain’s resolver answers.
• Page-speed check — runs Lighthouse against the URL on a slower schedule.

These are opt-in via the monitor_tls, monitor_dns, and monitor_page_speed flags at create time.

What you can configure

Concern	Settings
Request	method, URI, custom headers, request body, content type, follow-redirects
Auth	Basic, Digest, or Bearer token
Assertions	success/failure status code lists, keyword search (substring or regex, optionally case-sensitive or inverted), timeout
Schedule	run interval (30 s on paid plans, otherwise 60 s minimum), check regions, minimum healthy regions
Notifications	one or more notification groups

Full field-by-field reference: see the auto-generated POST /http/job.

Next steps

Quickstart Create your first HTTP check in 5 minutes.

Settings reference Every field on an HTTP check, explained.

API: Create HTTP monitor POST /http/job — the underlying endpoint.