HTTP check
Confirm an endpoint responds correctly to prove the install worked.
An HTTP check requirement confirms that a URL responds the way it should — it's both a step the installer completes and the verification itself. Inboard probes the endpoint and passes the step when the response matches what you expect.
When to use it
Use an HTTP check when success is observable over the network: a health endpoint returns 200, a page contains your snippet, or an API returns the expected payload. It's also the natural verifier to pair with other requirement types whose result shows up at a URL.
How to configure it
You define what Inboard probes and what counts as success:
- URL — the endpoint to request. Use a variable like
{{domain}}so it's per-installer. - Expected response — status code and, optionally, a string or value the body must contain.
GET https://{{domain}}/.well-known/acme-health
Expect: 200 and body contains "ok"A curl-style equivalent of the probe:
curl -sS https://{{domain}}/.well-known/acme-health
# => {"status":"ok"}How it's verified
By definition this requirement is verified by the HTTP check itself: Inboard makes the request and passes the step automatically when the response matches. No self-report is needed when the probe succeeds.