Getting started

A job is a URL, a method and a schedule. The service makes the request on time, records the status code and the timing, and leaves the response body alone.

Creating one takes a URL and a schedule. Everything else has a working default: GET, a ten second timeout, and no headers.

A first job

A five minute health check, written as a cron expression:

URL       https://api.example.com/health
Method    GET
Schedule  */5 * * * *   (cron, Europe/Berlin)

The form shows the next five runs as the expression changes, so a wrong field shows up before the job is saved rather than at two in the morning.

What counts as working

A 2xx status is a success. Anything else is a failure, including a redirect, which is recorded and not followed. Three retries follow a failed run, spaced one minute, five minutes and thirty minutes apart. A fourth failure pauses the job and sends one email with a resume link.

Limits

Fifty jobs per account, eight headers per job, a 16 KiB body, and a minimum interval of sixty seconds. A new account runs five jobs at a five minute minimum for the first day.