Creating HTTP monitors

Overview

HTTP monitors check website and API availability by making HTTP requests and validating responses. They verify that the server returns a successful response (status 200-299, plus any custom "up" codes you add).

Creating an HTTP monitor

1. Navigate to Uptime in the sidebar
2. Click Create monitor
3. Select HTTP/HTTPS as the monitor type
4. Enter the target URL (include https:// or http://)
5. Configure the settings below
6. Click Create monitor

Configuration options

• Name: A descriptive name for the monitor (max 50 characters)
• URL: The full URL to monitor (must include protocol)
• Request method: GET (default) or HEAD. HEAD fetches headers only — useful for large pages — but can't be combined with response body matching
• Custom "up" status codes: Treat additional status codes (e.g. 401, 403) as up instead of down, for endpoints that answer with an expected error code
• Check interval: How often to check (15 seconds to 30 minutes)
• Ignore TLS errors: Skip SSL certificate validation if needed
• Proxy: Route this monitor's checks through a proxy — see Outbound proxies

Response validation

Turn on Advanced matching to validate the response body:

• Match method — Equal, Include, or Regex.
• Expected value — the string (or regex) to match.
• JSON path — optional JMESPath expression. If set, Checkmate parses the body as JSON, evaluates the expression, and compares the result against Expected value. Leave blank to match the raw body.

See Response body matching for details.

Advanced matching still runs on responses that pass via a custom "up" code, so body checks aren't silently bypassed.

Related articles