HTTP Checks

HTTP monitors send an HTTP request to a URL on each check interval and validate the response against your criteria.

Setup Guide

1. Navigate to Monitors and click New Monitor.
2. Select HTTP as the check type.
3. Enter the full URL including the scheme (e.g. https://api.example.com/healthz).
4. Choose the HTTP method (GET is the default and works for most health endpoints).
5. Set the expected status code or range (e.g. 200 or 2xx).
6. Optionally add a body match string or regex to validate the response content.
7. Click Save.

Tip

For health endpoints that return JSON, use a body match like "status":"ok" to verify the response content, not just the status code.

Configuration

Field	Description	Default
URL	The full URL to request (including scheme).	Required
Method	HTTP method: GET, POST, PUT, DELETE, HEAD, OPTIONS.	GET
Expected Status	Status code or range (e.g. 200 or 2xx).	2xx
Body Match	A string or regex the response body must contain.	None
TLS Verification	Whether to verify the server’s TLS certificate.	Enabled
Follow Redirects	Whether to follow HTTP 3xx redirects.	Enabled
Timeout	Maximum wait time for the response.	10s

Authentication

You can add custom headers to your HTTP check for authentication:

headers:
  Authorization: "Bearer your-token-here"
  X-Custom-Header: "value"

Configure headers in the monitor’s Advanced section.

Request Body

For POST or PUT checks, you can specify a request body and content type:

{
  "content_type": "application/json",
  "body": "{\"ping\": true}"
}

TLS Certificate Expiry

HTTP monitors automatically track the TLS certificate expiry date of the target. YipYap will fire a warning alert when the certificate is within 14 days of expiring. You can customize this threshold in the monitor settings.

Example: Health Endpoint

A typical configuration for monitoring a health endpoint:

• URL: https://api.example.com/healthz
• Method: GET
• Expected Status: 200
• Body Match: "status":"ok"
• Interval: 30 seconds
• Timeout: 5 seconds
• Confirmation Threshold: 3