4.12Which assertions each monitor type supports
D means you can add it in the dashboard or through the API. A means through the API only. A dash means not supported.
| Assertion | URL | API | Multi-step (per step) | Browser | TCP | UDP | DNS |
|---|---|---|---|---|---|---|---|
status_code | D | D | D | A | — | — | — |
body | D | D | D | A | — | — | — |
header.<Name> | D | D | D | — | — | — | — |
json.<path> | A | A | A | — | — | — | — |
json_schema | D | D | D | — | — | — | — |
response_time_ms | D | D | D | A | D | D | A |
tls.days_until_expiry | A | A | A | — | — | — | — |
redirect.count | D | D | D | — | — | — | — |
redirect.final_url | D | D | D | — | — | — | — |
security.score | D | D | D | — | — | — | — |
no_console_errors | — | — | — | A | — | — | — |
- Browser monitors accept only
status_code,body,response_time_msandno_console_errors. Any other type is refused when you save. In the dashboard, useassert_visibleandassert_textsteps (chapter 7). - DNS monitors use expected values (chapter 6). Response time is their only assertion, through the API.
- Ping, TLS certificate, domain expiry and heartbeat monitors take no assertions. Their own settings decide the result (chapter 2).