Check an API for a status, a word, or a JSON field.
An HTTP monitor loads a URL and can require a status code, text that must appear, text that must not, or one JSON field with an expected value. A failure is checked again before anyone is alerted.
Keyword and JSON assertions
The body can be required to contain a phrase, or to omit one. A JSON check names one field and the value it should have. Custom headers, an Authorization header, and a request body are stored encrypted and are not shown again after you save them.
Slow is not down
A slow threshold marks the monitor degraded without paging you for an outage. A timeout, a wrong status, or a missing phrase is a failure, and that failure is confirmed before the incident says the API is down.
What this does not do
One check follows one URL. It is not a multi-step browser script, and browser checks are not offered. UPKira probes from one region. Page speed is a separate monitor type, with its own hourly and daily limits.
Questions people ask first
Can one monitor check several JSON fields?
No. One HTTP monitor checks one JSON field. Add another monitor for a second field.
Does a single 500 send an alert?
Not by itself. UPKira checks the URL again. Only a confirmed failure opens the incident.