Servilo Pulse Docs
Home Get started

HTTP / API monitors

Pings a URL and checks the response. Use it for websites, health endpoints and JSON APIs.

Fields

Field Required Description
URL Yes The endpoint to request, e.g. https://example.com/health.
Method No GET (default), POST, HEAD or PUT.
Success condition No An expression such as statusCode == 200. When set, the check passes only if it evaluates true.
Body contains No A keyword that must appear in the response body, e.g. ok.
JSON path No A dotted path into a JSON response, e.g. data.status.
JSON expected value No The value the JSON path must equal, e.g. healthy.

How the check passes

The check is considered UP when all configured assertions hold:

  1. The request completes, and
  2. the success condition (if set) is true, and
  3. the body contains keyword (if set) is present, and
  4. the JSON path value (if set) equals the expected value.

If you leave the optional fields blank, a normal successful HTTP response is treated as UP.

Examples

Basic health check

URL:              https://api.example.com/health
Success condition: statusCode == 200

JSON health endpoint returning { "data": { "status": "healthy" } }

URL:                 https://api.example.com/status
JSON path:           data.status
JSON expected value: healthy

Keyword check for a marketing page

URL:            https://example.com
Body contains:  Welcome

Tip

Prefer a dedicated /health endpoint over your homepage. It's cheaper to serve and lets you assert on a small, stable payload.