Endpoint checks

Uptime checks watch your homepage. Endpoint checks watch the URLs that matter most on your site: an API health route, the login page, checkout, a webhook receiver's status page or a sitemap.

What an endpoint check does

On your plan's uptime interval (every 15 minutes on Free), Wardzo sends one GET or HEAD request to the URL and checks:

• Status: the exact HTTP status you expect, or any 2xx/3xx if you leave it empty. If you expect a redirect (301, 302 and so on), Wardzo does not follow it.
• Text (optional, GET only): a snippet that must appear in the response, for example "status":"ok".
• Response time (optional): fail if the response takes longer than a limit, for example 2000 ms.

When a check fails, Wardzo checks again one minute later. Only if the second check fails too do you get an email alert. You get another email when the check passes again. Alerts follow your alert settings.

What it never does

Endpoint checks are read-only. Wardzo never submits forms, never sends a request body, cookies or credentials, and only checks URLs on websites you monitor in your account. Private and internal addresses are always blocked.

Add a check

• Dashboard: open a site in your dashboard, scroll to Endpoint checks and add a URL or path such as /api/health.
• AI agent: with the Wardzo MCP server, ask your agent to "add an endpoint check for /api/health on mysite.com that must contain ok". Use the add_endpoint, list_endpoints and remove_endpoint tools.

Limits per plan

Plan	Endpoint checks	Interval
Free	2	every 15 min
Basic	10	every 5 min
Premium	50	every minute
Scale	150	every minute

Tips

• Point checks at a lightweight health route that also checks your database, so a check fails when your app is really broken.
• Use a text check for pages that return 200 even when they show an error, such as many single-page apps.
• If your firewall blocks bots, allow the WardzoBot user agent. See WardzoBot.