API Endpoint Checker

What it does

The API Endpoint Checker sends a single request to the endpoint you enter and checks the response against the pass conditions you set. Unlike an uptime ping, it doesn't just confirm the server answered — it can verify the exact status code, the response time, a substring in the body, and a value at a JSON field path.

Choose the HTTP method (GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS), add any request headers (such as an Authorization token) and, for write methods, a request body. The check passes only when every condition you set is met.

How to use it

1. Enter the endpoint URL (e.g. https://api.example.com/health) and choose the HTTP method.
2. Open "Request options" to add headers (one per line, e.g. Authorization: Bearer xxxxx) and a request body for POST/PUT/PATCH.
3. Under "Pass conditions", set any of: expected status code, max response time, text the body must contain, and a JSON field path (optionally equal to a value). Leave a field blank to skip it.
4. Press Check. Read the Pass / Fail / Unreachable result, the response summary, and the per-condition pass/fail list.

What the results mean

Result	What it means
Pass	The endpoint responded and every pass condition you set was met. (With no conditions set, any non-error 2xx/3xx response passes.)
Fail	The endpoint responded, but at least one pass condition was not met — see which one in the conditions list.
Unreachable	No HTTP response at all — the request timed out, DNS failed, the connection was refused, or there was a TLS error. See the reason shown.

Errors & warnings explained

Message	What it means
Unexpected status code	The endpoint returned a status code different from the one you required.
Slower than the limit	The response was slower than the maximum response time you set.
Text not found in body	The "body contains" text you required did not appear in the response body.
Response body was not valid JSON	You set a JSON field condition, but the body could not be parsed as JSON.
JSON field not found	The JSON field path you entered does not exist in the response.
JSON field had a different value	The JSON field exists but its value did not equal the one you required.
Connection timed out	No response within the time limit — the endpoint is slow or unreachable.
DNS error	The domain could not be resolved. Check the spelling, or the host's DNS may be down.
SSL/TLS error	The secure connection couldn't be completed — often a certificate problem.

Good to know

• Free, no login, and we don't store the URL, headers, body or response you check.
• Rate limited to about 6 checks per minute per network.
• One request per check from our European location — no scheduling or history.
• For continuous checks with email alerts when a condition fails, add the endpoint as an API monitor in a free account.

Related guides

• Uptime Checker
• Response Time Checker
• Website Growth Check