ismysiteup
FeaturesPricingToolsIs it down?BlogSign InGet Started
ismysiteup

All-in-one website monitoring: uptime, widgets, servers and APIs, with alerts on WhatsApp, Telegram, Slack and email. Know before your client does.

contact@ismysiteup.netInstagram

Product

  • Uptime monitoring
  • Apps & Widgets
  • Server monitoring
  • API tools & Data Monitors
  • Pricing

Resources

  • Free tools
  • Is it down?
  • Blog
  • HTTP status codes
  • API docs
  • Alert channels
  • Compare

Legal

  • Terms of Service
  • Privacy Policy

© 2026 Sea Jay Media Digital Marketing LLC. All rights reserved.

The service is provided as is. See the Terms.

HomeBlogHow-To GuidesHow to Monitor API Endpoints Without Code: Tests & Assertions
How-To Guides

How to Monitor API Endpoints Without Code: Tests & Assertions

October 31, 2026
10 min read

Written by ismysiteup

If you want to know how to monitor API endpoints properly, checking that they answer with a 200 isn't enough. An API can respond quickly with a 200 status and still send back an error object, an empty list, or the wrong content type. The fix is an endpoint test: a request that runs on a schedule, checks the response against a set of rules called assertions, and alerts you when any rule fails. This guide covers which assertions to use, which endpoints to watch, and how to set it all up without writing code.

What is API endpoint monitoring?

API endpoint monitoring means sending a real request to an API route on a schedule and checking that the response is correct, not just that something answered. A typical check confirms that:

  • the endpoint responds at all (no timeout, DNS failure, or refused connection)
  • the status code is the one you expect
  • the response arrives fast enough to be usable
  • the body holds the data you expect, such as "status": "ok" or a non-empty list
  • key headers, such as Content-Type: application/json, are correct

This is also called synthetic API monitoring, because the monitor sends its own test requests whether or not real users are calling the API. It's different from observability tools that read your real traffic, and it catches problems even when nobody is using the API.

If you're new to the idea that a 200 can still hide a failure, start with our short explainer, why an HTTP 200 isn't always healthy.

API monitoring vs API testing

The two use the same building blocks (a request plus assertions), but they answer different questions.

API testing API endpoint monitoring
When it runs Before release, in development or CI All the time, on a schedule, in production
Question it answers "Does this code work?" "Is it still working right now?"
Who acts on a failure The developer who changed the code Whoever gets the alert
Typical scope Many cases, edge cases, test data A few critical checks per endpoint

Tests passing on deploy day don't stop an expired third-party key, a full disk, or a database migration from breaking the API next Tuesday. Scheduled API tests in production catch those.

The 6 assertions every API endpoint check should consider

An assertion is a single rule the response must pass, for example "status equals 200" or "response time is less than 800 ms". A check passes only when every assertion passes. In ismysiteup, endpoint tests support six assertion types:

Assertion type What it checks Example rule What it catches
status The exact HTTP status code status eq 200 500 errors, 404s after a route change, 401s from an expired token
status_range The status falls within a range status in the 2xx range Any non-success response when several 2xx codes are valid
response_time How long the response took, in ms response_time lt 800 Slowdowns before they turn into timeouts
body_contains Text anywhere in the response body body contains "healthy":true Error pages, maintenance notices, login pages served with a 200
body_json_path One value inside the JSON response status eq ok; item count gt 0 Empty results, error objects, wrong values, schema changes
header_contains A response header's value Content-Type contains application/json An HTML error page in place of JSON, a missing cache or CORS header

You combine these with operators: eq, neq, lt, gt, lte, gte, contains, not_contains, and matches for pattern matching.

Status code assertions: status and status_range

Use status when exactly one code is right, such as a health endpoint that should always return 200. Use status_range when several codes are fine, such as an endpoint that may return 200 or 204. If you're unsure what a code means, our guide to HTTP status codes explained covers the common ones.

Response time assertions

A response time assertion turns "the API feels slow" into a clear alert. Set the limit with some headroom over your normal response time. If an endpoint usually answers in 200 ms, a limit of 800 ms or 1,000 ms catches real problems without alerting on every small spike.

JSON body assertions with body_json_path

This is the assertion that separates real API monitoring from a ping. Point it at one field in the JSON response and compare it with a value. For example, check that status equals ok, that a database field doesn't equal down, or that an item count is greater than 0.

Body and header assertions

body_contains and not_contains are good safety nets. Assert that the body does not contain "error" or Maintenance, or that it does contain a field name every good response has. header_contains catches a classic failure: a proxy or load balancer returning an HTML error page with a 200, when your clients expect application/json.

Which API endpoints should you monitor?

You don't need a check on every route. Start with the endpoints whose failure hurts most:

  1. Health or status endpoint. If you have /health or /status, make it check its dependencies (database, cache, queue), not just return a fixed "OK".
  2. Authentication. A login or token endpoint. If auth breaks, every other endpoint breaks for real users.
  3. Your most important read endpoint. The list of products, the user's dashboard data, whatever your app can't work without.
  4. A critical write path. Checkout, sign-up, or a form submission. Monitor it with care (see the tips below) so the monitor doesn't create junk records.
  5. Third-party APIs you depend on. Payment providers, shipping rates, or an AI API.

How to monitor API endpoints without code: step by step

Here's how to set this up in ismysiteup. The API Client and endpoint tests are included on every plan, including Free.

Step 1: Build and send the request in the API Client

Open the built-in API Client, a Postman-like tool for building and saving requests. Choose the method (GET, POST, PUT, PATCH, DELETE, HEAD, or OPTIONS) and enter the endpoint URL. Add a body if needed (JSON, raw, x-www-form-urlencoded, or form-data) and set authentication: bearer token, basic auth, or an API key. Send it and look at a real, healthy response. That response is your template for the assertions.

You can organize saved requests into projects, folders, and environments, which is handy if you manage several APIs or separate staging and production.

Step 2: Write down what "healthy" looks like

From the healthy response, note:

  • the status code
  • the normal response time
  • one or two JSON values that prove the request really worked
  • the Content-Type header

Step 3: Create an endpoint test with assertions

In DevTools, open Monitor Endpoints to create a scheduled test with assertions. A solid starting set for a JSON API:

  • status eq 200
  • response_time lt 1000
  • header_contains Content-Type contains application/json
  • body_json_path on your key field, e.g. status eq ok
  • a body check with not_contains "error"

Four or five assertions per endpoint is plenty. More rules mean more alerts to read, not more safety.

Step 4: Choose where alerts go

When a check fails, you need to see it. ismysiteup sends alerts by WhatsApp, Telegram, Slack, and email on every plan. Set up the channel you actually read with our guides for Telegram downtime alerts, WhatsApp alerts, or the Slack alerts guide.

Step 5: Add a plain uptime monitor for the basics

For your main health endpoint, also add a regular uptime monitor with an expected status code. Uptime checks run every 5 minutes on Free, every minute on Pro, and every 30 seconds on Business, and you'll also get warnings before your SSL certificate expires. If you prefer to manage monitors in code, the ismysiteup REST API docs show how to create, pause, and list monitors with an API key.

When the API works but the numbers are wrong: Data Monitors

Assertions check that a response is correct right now. Some failures only show up over time: orders per hour drop from 42 to 0, sign-ups flatline, or a queue keeps growing. Every single response looks valid, but the business has stopped.

That's what Data Monitors are for. A Data Monitor watches a value inside an API's JSON response and alerts you when it changes, goes up, goes down, or crosses a number you set. Free includes one Data Monitor with three watched fields, checked hourly. Pro and Business check more often. We walk through a full setup in how to detect silent failures.

A simple rule of thumb:

  • Endpoint tests answer "Is this response right?"
  • Data Monitors answer "Is this number moving the way it should?"

API endpoint monitoring best practices

  • Use a dedicated, read-only API key for monitoring, with the least access possible, and rotate it like any other secret.
  • Don't let write checks create junk. Point POST checks at a test account or a dry-run endpoint, or monitor the read side of the flow.
  • Assert on meaning, not exact text. Check status eq ok rather than the whole body, which changes with timestamps and IDs.
  • Set realistic time limits from your normal response time, not a guess.
  • Group checks by client or project so an alert tells you right away whose API is affected. See how to monitor client websites for an agency setup.

Start monitoring your API endpoints

ismysiteup includes the API Client, endpoint tests, five uptime monitors, and one Data Monitor on the Free plan, with alerts on WhatsApp, Telegram, Slack, and email. Pro is listed at $9/month and Business at $24/month. See the pricing page for current details and availability. Want a quick look first? Paste any URL into the free instant checker to see its status code, response time, and SSL details.

Start monitoring your API for free. No credit card needed.

FAQ

What is endpoint monitoring?

Endpoint monitoring is sending requests to an API route or URL on a schedule and checking the response, including its status code, response time, body, and headers. When something is wrong, you get an alert before your users notice.

How do I monitor API endpoints?

Pick your critical endpoints, send a request to each one to see a healthy response, then create a scheduled check with assertions for the status code, response time, and a key JSON value. Connect an alert channel you read, such as Slack, Telegram, WhatsApp, or email.

How do I check if an API endpoint is working?

Send a request with an API client or curl and check three things: the status code is 2xx, the response came back in a reasonable time, and the body holds the data you expect. A 200 with an empty or error body is not a working endpoint.

What is an assertion in API monitoring?

An assertion is a rule the response must pass, such as "status equals 200", "response time is less than 800 ms", or "the JSON field status equals ok". A check passes only when every assertion passes.

What is a good API response time?

It depends on the endpoint, but many teams aim for under 500 ms on common read requests and accept more for heavy reports or searches. Measure your normal time first, then set an alert limit with headroom above it.

What's the difference between API monitoring and API testing?

API testing checks your code before release, usually in CI. API monitoring runs similar checks on a schedule in production, so you find out when a working API breaks because of an expired key, a failing dependency, or a server problem.

Sources

  • RFC 9110: HTTP Semantics, RFC Editor
  • HTTP response status codes - HTTP | MDN, MDN Web Docs
  • Monitor health and performance of your APIs in Postman | Postman Docs, Postman
  • Checkly Pricing Plans: Flexible Synthetic Monitoring Solution, Checkly

On this page

  • What is API endpoint monitoring?
  • API monitoring vs API testing
  • The 6 assertions every API endpoint check should consider
  • Status code assertions: status and status_range
  • Response time assertions
  • JSON body assertions with body_json_path
  • Body and header assertions
  • Which API endpoints should you monitor?
  • How to monitor API endpoints without code: step by step
  • Step 1: Build and send the request in the API Client
  • Step 2: Write down what "healthy" looks like
  • Step 3: Create an endpoint test with assertions
  • Step 4: Choose where alerts go
  • Step 5: Add a plain uptime monitor for the basics
  • When the API works but the numbers are wrong: Data Monitors
  • API endpoint monitoring best practices
  • Start monitoring your API endpoints
  • FAQ
  • What is endpoint monitoring?
  • How do I monitor API endpoints?
  • How do I check if an API endpoint is working?
  • What is an assertion in API monitoring?
  • What is a good API response time?
  • What's the difference between API monitoring and API testing?
  • Sources

Tags

API monitoring
HTTP status codes
response time
uptime monitoring
web development

Share this article

TweetLinkedIn

Related Posts

How-To Guides

Monitoring Your API: Why an HTTP 200 Isn't Always 'Healthy'

A server can return '200 OK' while quietly serving broken data. Here's what real API monitoring looks like and how to set it up.

June 24, 2026·2 min read
How-To Guides

Website Down for Maintenance? How to Tell (and Do It Right)

Is a website down for maintenance, actually broken, or only down for you? Here's how to tell in under a minute, plus how to serve a proper 503 maintenance page with Retry-After on nginx, Apache, and WordPress.

October 27, 2026·11 min read
How-To Guides

Why Is My Website Down? 10 Causes and a Fix-It Checklist

Site won't load and it's not just you? Here's why your website is down, plus a 10-step troubleshooting checklist to find the cause and get it back online fast.

October 30, 2026·10 min read
How-To Guides

How to Check If an App Is Down (or If It's Just You)

Here's how to check if an app is down for everyone or just you: a 60-second outside check, a 7-step checklist for when it only fails for you, and service-specific tips for ChatGPT, Instagram, WhatsApp and more.

November 18, 2026·10 min read

Monitor your websites for free

Get instant email, Telegram, and WhatsApp alerts when your sites go down. Free plan checks every 10 minutes. No credit card required.

Start Monitoring Free