7.2Which monitor should I use?
Pick the simplest monitor that answers your question. The dashboard shows a short description for each type.
| You want to know… | Use | The dashboard says |
|---|---|---|
| Does the page load and answer correctly? | url (2.2) | "GET/POST a URL on a schedule and assert on the response." |
| Does one API call return the right data? | api (2.3) | "A single request with richer body and JSON assertions." |
| Does a chain of API calls work together? | api-multistep (2.4) | "An ordered chain of requests sharing a cookie jar and extracted variables." |
| Can a visitor click, type and finish a task, such as signing in, signing up or checking out? | browser (this chapter) | "Drive a real browser through a scripted flow with secret references." |
A URL or API monitor sees only the server's answer. A browser monitor sees the page after it has finished loading in the browser. Use it when the page can load but still be broken for people, for example when the sign-in button does nothing.
- Browser monitors need a plan that includes them (see 7.12). If your plan does not, the dashboard offers a link to use a URL check instead.
- Each browser check uses one of your plan's browser runs. URL and API checks do not. Keep browser monitors for your most important tasks.