Crowswatch

Web & API Watch

Your site looks fine. Your checkout is broken.

The homepage loads, so everything looks normal. Meanwhile the page that takes payment or the endpoint that logs people in has stopped working. Web & API Watch runs website and API checks on the pages your customers actually use and tells you what broke.

Get startedTalk to us
  1. 1Checks what your customers actually use
  2. 2Tells you what broke, not just that something did
  3. 3Alerts after the failure time you set
Example only. Hollowmoor is fictional.

How it breaks quietly

  1. Step 1

    Something changes

    A release, a plugin update or a provider problem breaks one part of your site or API.

  2. Step 2

    The site still loads

    The homepage looks normal, so a quick look tells nobody anything is wrong.

  3. Step 3

    Customers get stuck

    The order button is missing, the login call fails or the product feed stops answering.

  4. Step 4

    You find out from them

    Orders drop and complaints arrive before anyone on your team has spotted the problem.

A page that loads is not the same as a page that works

Web & API Watch checks for the words that should be on the page and the answer your API should give, not just that something came back.

What it checks on your website and API

Add the pages and endpoints that matter to your customers, and choose what a pass looks like for each one.

The page loads (HTTP status)

Fails when a page answers with an error, or with a different status from the one you expect.

The right words are on it (Text match)

Fails when text that should be there is missing, such as 'Place order' on your checkout or 'Sign in' on your login page.

Your API gives the right answer (Status code and JSON checks)

Send GET, POST, PUT, PATCH, DELETE or HEAD with your own headers and body, then check the status code and values in the JSON response.

It answers in time (Response time)

Set a maximum response time and a slow answer counts as a failure.

It ends up in the right place (Redirects)

Follow redirects and check the page lands on the address you expect.

How it has been doing (History)

A timeline, a response time chart and a log of every check, with the reason for each failure.

How it alerts you

One alert when a check crosses the line you set, with the reason it failed.

Only for failures that last

Choose how long a check must keep failing before you hear about it, from five minutes to four hours.

When it is fixed

A second alert tells you the check is passing again. It is on unless you turn it off.

Where alerts go

Email on every plan, and Slack on paid plans.

Questions

What can I check?Show

Any public page or API endpoint. Check that a page loads, that it contains the text you expect, or that an endpoint returns the right status code and JSON values.

How often are checks run?Show

You choose for each check, from every 15 minutes to once a day. New checks run every 30 minutes.

Can it check pages behind a login?Show

Not yet. Checks run without signing in, and Authorization and Cookie headers are not sent. An API that takes a key in a header of its own, such as X-API-Key, can be checked.

Does it run the JavaScript on my pages?Show

No. It reads the page as your server sends it, so text that only appears after scripts run in the browser will not be found.

What if my site blocks the check?Show

A check that is blocked or challenged by your firewall shows as protected, and it does not count towards an alert.

How many checks can I have on each plan?Show

Five on the Free plan, 100 on Standard and 250 on Professional. Talk to us if you need more.

Know when the part that matters stops working

Start free with five checks.

Get startedTalk to us

Other Crowswatch products

  • Brand Watch

    Fake shops found and taken down for you

  • Domain Watch

    DNS, SSL, email authentication and expiry on the domains you own

  • Status Watch

    Incidents at the providers your business runs on