HTTP monitors send a real request to your URL on a schedule and record whether the response matches your expectations. If it doesn’t, an incident is created and your team is notified.
Setting up a monitor
In your project, click Add monitor and choose HTTP / HTTPS. Fill in:
URL — the full address to check, including https://. Watchplane follows redirects by default.
Check interval — how often to run the check. Options range from every 30 seconds (Pro/Business) to every 3 minutes (Free).
HTTP method — defaults to GET. Use POST, PUT, or others if you need to hit an endpoint that only accepts certain methods.
Request headers — add any headers your endpoint requires, such as Authorization, Accept, or custom headers for internal services.
Request body — for POST/PUT requests, paste the body you want sent (JSON, form data, etc.).
Assertions
Assertions define what a passing response looks like. If you add no assertions, any response that arrives counts as up — even a 500 error. In most cases you’ll want at least a status code check.
See Assertions for the full guide on what you can check.
SSL certificates
For any https:// monitor, Watchplane automatically tracks the TLS certificate expiry date. You’ll receive an alert when the certificate is within 30 days of expiring — no extra configuration needed.
Response time tracking
Every check records the response time. The monitor detail page shows a response time chart so you can spot slowdowns over time, even before they become outages.
Availability history
The monitor page shows your uptime percentage for the last 24 hours, 7 days, and 30 days, along with a timeline of all incidents.
Developers: For the full configuration schema, programmatic creation, and response metrics API, see the API Reference.