Run scheduled HTTP checks and validate status codes, headers, response bodies, JSON paths, and latency on every response.
An API can return 200 OK while its payload is empty, stale, or shaped incorrectly. pingdan evaluates multiple assertions after each request and stores the exact failure detail. You see whether the transport, contract, data, or performance failed instead of starting an incident with a generic red light.
Add the API URL and HTTP method, then set an interval from one minute to seven days.
Require a status and combine header, body, JSON path, or response-time comparisons.
Use thresholds to filter transient errors and route down and recovery events to your team.
Build checks that expose contract, dependency, data, and performance failures.
Read guide →Validate nested fields and arrays so a plausible but incorrect payload cannot pass.
Read guide →Choose the right expected status and decide how redirects and error families should behave.
Read guide →At minimum, validate the expected HTTP status, a stable field or value in the response, and a response-time ceiling. Critical APIs may also need header and multiple JSON field assertions.
Many APIs return 200 for application-level errors or malformed data. A status-only monitor reports healthy even when clients cannot use the response.
Yes. JSON path assertions resolve dotted paths, including array indexes such as items.0.id, and compare the resulting value with the target you define.
Checks can run once per minute. Your failure threshold controls how many consecutive failures are required before the endpoint is marked down and an alert is sent.
Create your first monitor in under a minute. Every feature is free.
Create a free monitor