Website check Beta
POST /api/v1/monitors
Type http: fetch a URL and decide whether the page is healthy. This is the default, and what every monitor created before check types existed uses.
There is no separate endpoint for this: it is the ordinary create a monitor call with type set to "http". The same settings apply when you update a monitor with PATCH /api/v1/monitors/{id}.
Every type shares the same interval, retries, alerting, maintenance, results and reports. Only the settings below differ. See Check types for how the nine types compare.
Up or down
- A 2xx or 3xx response counts as up; 4xx and 5xx count as down.
- If
shouldContainis set, the body must contain that exact text, and ifshouldNotContainis set it must not. Both are case-sensitive. - If
verifyCertificateis on, an invalid certificate is a failure. WithsslDownDays, the site counts as down that many days before the certificate expires. - Classic bot-protection codes are re-confirmed through a real-browser fingerprint before a healthy site is called down.
Settings that apply
| Setting | Notes |
|---|---|
url | The page to fetch, http:// or https://. |
shouldContain, shouldNotContain | Text the body must or must not contain. |
postData | Send a POST with this body instead of a GET. United Kingdom location only. |
requestHeaders | Up to 20 extra headers. |
authUsername, authPassword | HTTP basic authentication. |
verifyCertificate, sslDownDays | Certificate rules. |
regions | Where the check runs from. |
timeoutSeconds | How long to wait. |
Create one
type can be left out: a monitor with no type is an http check.
Related
- Custom status page: read a field from your own status document
- Monitor settings: every field in full
- Check types: the other eight types