Validate status codes
Define which HTTP responses count as successful for your endpoint.
← Clesk Uptime
API monitoring
Monitor the endpoints your product depends on.
Check HTTP and HTTPS endpoints regularly for availability, expected status codes, response time, response headers and an optional text value or JSON field.
Track response times
See hard outages as well as unusual performance trends.
Check content
Keyword, JSON field and header checks detect unexpected or incomplete responses, even while the status code is still 200.
For health endpoints and public APIs
Clesk Uptime covers HTTP health checks including JSON field assertions (e.g. $.status equals ok) and response header checks. Complex browser flows and authenticated transactions are not part of the current feature set.
- ✓Health and readiness endpoints
- ✓Public REST endpoints
- ✓Webhooks and integration targets
Set up in three steps
- 1
Add the endpoint
Create a monitor with the URL of your health or API endpoint.
- 2
Define expectations
Set the expected status codes, optionally an expected text (keyword) in the response.
- 3
Wire up alerts
Pick email, Slack, Discord or webhook; confirmed deviations trigger the alert.
FAQ
Can I define an expected HTTP status?
Yes. You can configure multiple expected status codes.
Does Clesk Uptime support JSONPath checks?
Yes. You can assert a JSON field via path (e.g. $.status equals ok) and additionally check a response header against an expected value. Wildcards and filter expressions are not included.
How does API monitoring differ from website monitoring?
Technically both are HTTP checks. For APIs, expected status codes and response times matter most; for websites, the visible content does too (keyword check).
Can I monitor internal APIs?
The endpoint must be reachable from the internet. For purely internal jobs without a public endpoint, heartbeats are the right tool.
One HTTP endpoint is enough to get started.
Create the monitor and receive an instant alert when failures are confirmed.
Monitor for free