Monitors & detections
Choose what a healthy response looks like
Set an HTTP method and the status codes your monitor should accept.
Reviewed
Start with a read-only check
Open a monitor’s editor and expand Request. GET reads the endpoint. HEAD checks headers without a response body, so it cannot be combined with response-text or JSON rules.
POST, PUT, PATCH and DELETE are also available. These can change data on every scheduled or manual check. Use them only with an endpoint designed to be called repeatedly for monitoring.
Choose healthy HTTP codes
In HTTP settings, Healthy HTTP codes accepts individual codes or ranges, separated by commas. Codes must be between 200 and 599; up to 20 entries are allowed. The default is 200-399.
For an API that must return success rather than redirect, choose 200-299. To accept exactly 200 or 204, enter 200, 204. Accepting an error code deliberately will make it healthy for this monitor; choose only the responses that mean your service is working.
- Open HTTP settings in the monitor editor.
- Enter 200-299 in Healthy HTTP codes.
- Save, then use Check to inspect a fresh result.
Status is the first part of the answer
A healthy code must also pass any enabled response-text and JSON rules. A 200 response can still fail if the expected content is missing. With Follow redirects enabled, the destination response is evaluated; without it, the redirect response itself is evaluated.