Documentation  〉How to automate check enable/disable and maintenance

There's no maintenance scheduling feature built-in in updown at the moment but you can automate it on your side using the API to disable and enable the check at the time you want (for example at the beginning and end of a maintenance script, or at a fixed time in a cron task)

Using the curl command you can do it this way:

curl -X PUT -d 'enabled=false'

You can find your API key on the API page and your check "token" is a 4 letter identifier you can find from the URL of your status pages (for example → the token is "ngg8") or from the API using the /checks call.

Alternatively if it's not too often you can simply use the interface to manually disable the check before and re-enable it after the maintenance window, using the toggle on the left of check edit form:

screenshot of updown dashboard showing the on/off toggle

While the monitoring is disabled, no requests will be performed so updown will not detect any downtime or send any alert. The status of your website (in the UI / status page) will simply stay the same as it was on the last check (no matter if it was up or down). As a result a disabled check also won't cost any credits.

Rather mute?

Alternatively, you can mute the notifications without disabling the monitoring, this is done by setting the "mute_until" attribute from the API, you can set it to a specific time or "recovery" (waits until recovery during a downtime) or "forever". Using the same endpoint PUT /api/checks/:token endpoint, example:

curl -X PUT -d 'mute_until=2021-10-05T22:26:12-04:00'

If you want to resume notifications before the specified time, you can update again the mute_until to an empty string. In this case any downtimes will be recorded but no notification will be sent.

Here is an example of a small PHP utility page made (and kindly shared) by one of our clients to bulk mute their checks.

Adrien Rey-Jarthon
Created on October 17, 2023 · Last update on November 05, 2023 · Suggest changes to this page