Scheduled Account Rebaseline

If your webpages change on a predictable schedule, for example content that is published every working day, you can rebaseline your whole account automatically instead of doing it from the portal. This guide sets up a small Linux VM that calls the WebOrion Monitor API every weekday at 5:30 PM and rebaselines every active webpage in your account.

How it works

A short bash script makes two API calls:

List webpages (GET /api/v1/urls) to get the ID of every active webpage in the account.
Create batch rebaseline job (POST /api/v1/batch_jobs/rebaseline) with those IDs.

Cron runs the script on a schedule. Each run creates a batch job that you can track in the portal under Batch Jobs → View Batch Jobs, just like a bulk rebaseline started from the portal.

Rebaselining accepts the current state of each webpage as the new reference. If a webpage is defaced before the scheduled run and the alert has not been handled, the defaced version becomes the new baseline.

Before you begin

You will need:

An API token. Generate one in the portal under Account → Manage Credentials. The token acts as your user, so it can rebaseline any webpage your account can edit.
A Linux VM with outbound HTTPS (port 443) access to api.monitor.weborion.io. A small instance such as an AWS t3.micro or GCP e2-micro is enough.

The commands below are for Ubuntu 24.04. Notes for Amazon Linux 2023 are included where the steps differ.

Setup

Prepare the VM

Install the tools the script needs, set the timezone that the schedule should follow, and create a service user and folders for the script.

sudo apt update && sudo apt install -y curl jq cron
sudo timedatectl set-timezone Asia/Singapore
sudo useradd --system --create-home --shell /usr/sbin/nologin weborion
sudo mkdir -p /opt/weborion /etc/weborion /var/log/weborion
sudo chown weborion:weborion /var/log/weborion

Cron uses the VM’s system timezone, so set it to the timezone you want 5:30 PM to mean. Replace Asia/Singapore if you are elsewhere.

On Amazon Linux 2023, cron is not installed by default. Use sudo dnf install -y cronie jq and then sudo systemctl enable --now crond in place of the apt command above.

Store the API token

Save the token in a file that only the service user can read. Keeping it out of the script means you can rotate the token without editing any code.

sudo tee /etc/weborion/rebaseline.env >/dev/null <<'EOF'
WEBORION_API_TOKEN=paste-your-token-here
EOF
sudo chown weborion:weborion /etc/weborion/rebaseline.env
sudo chmod 600 /etc/weborion/rebaseline.env

Check the token and find your webpage IDs

Before automating anything, confirm the token works by listing your webpages. Every webpage has a numeric id, which is what the rebaseline API expects.

export WEBORION_API_TOKEN=paste-your-token-here

curl -sS -H "Authorization: Bearer $WEBORION_API_TOKEN" \
  https://api.monitor.weborion.io/api/v1/urls \
  | jq '(if type=="array" then . else .data end)[] | {id, url_name, config_name, health_status}'

Archived webpages are not included in this list, so they are never rebaselined by the script.To look up the ID of a single webpage by its URL, use Get a webpage by URL string:

curl -sS -X POST -H "Authorization: Bearer $WEBORION_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://www.example.com/"}' \
  https://api.monitor.weborion.io/api/v1/urls/get_by_url | jq '.id'

Create the rebaseline script

Create /opt/weborion/rebaseline.sh with the command below. The script lists every active webpage and submits them for rebaselining in batches of 200./opt/weborion is owned by root, so the file is written with sudo tee. Keep the quotes around 'EOF' so the script is saved exactly as shown. Without them, the shell expands the script’s variables while writing the file.

sudo tee /opt/weborion/rebaseline.sh >/dev/null <<'EOF'
#!/usr/bin/env bash
# Rebaseline every active webpage in a WebOrion Monitor account.
set -euo pipefail

source "${ENV_FILE:-/etc/weborion/rebaseline.env}"
: "${WEBORION_API_TOKEN:?WEBORION_API_TOKEN is not set}"
API_BASE="${WEBORION_API_BASE:-https://api.monitor.weborion.io}"
BATCH_SIZE="${BATCH_SIZE:-200}"

log() { echo "$(date '+%Y-%m-%d %H:%M:%S %Z') $*"; }

api() {
  curl -sS --fail-with-body --retry 3 --retry-delay 5 --max-time 120 \
    -H "Authorization: Bearer ${WEBORION_API_TOKEN}" \
    -H "Accept: application/json" \
    -H "Content-Type: application/json" \
    "$@"
}

log "Fetching webpages"
urls_json="$(api "${API_BASE}/api/v1/urls")"

total="$(jq '(if type=="array" then . else .data end) | length' <<<"$urls_json")"
if [[ "$total" -eq 0 ]]; then
  log "No active webpages found, nothing to do"
  exit 0
fi
log "Found ${total} active webpages"

jq -c --argjson n "$BATCH_SIZE" \
  '[(if type=="array" then . else .data end)[].id]
   | [range(0; length; $n) as $i | .[$i:$i+$n]][]' <<<"$urls_json" |
while read -r chunk; do
  count="$(jq length <<<"$chunk")"
  resp="$(api -X POST "${API_BASE}/api/v1/batch_jobs/rebaseline" -d "{\"url_ids\": ${chunk}}")"
  job_id="$(jq -r '.id' <<<"$resp")"
  log "Created rebaseline job RB$(printf '%05d' "$job_id") (API ID ${job_id}) for ${count} webpages"
done

log "Done"
EOF

Set the owner and permissions, then do a test run as the service user:

sudo chown weborion:weborion /opt/weborion/rebaseline.sh
sudo chmod 750 /opt/weborion/rebaseline.sh
sudo -u weborion /opt/weborion/rebaseline.sh

A successful run prints one line per batch job created, for example:

2026-10-01 17:30:01 +08 Fetching webpages
2026-10-01 17:30:02 +08 Found 312 active webpages
2026-10-01 17:30:03 +08 Created rebaseline job RB01234 (API ID 1234) for 200 webpages
2026-10-01 17:30:03 +08 Created rebaseline job RB01235 (API ID 1235) for 112 webpages
2026-10-01 17:30:03 +08 Done

The test run starts a real rebaseline of every webpage in the account. Run it at a time when that is acceptable.

Schedule it for weekdays at 5:30 PM

Add a cron entry that runs the script at 17:30, Monday to Friday, and appends its output to a log file.

sudo tee /etc/cron.d/weborion-rebaseline >/dev/null <<'EOF'
30 17 * * 1-5 weborion flock -n /tmp/weborion-rebaseline.lock /opt/weborion/rebaseline.sh >> /var/log/weborion/rebaseline.log 2>&1
EOF
sudo chmod 644 /etc/cron.d/weborion-rebaseline

flock stops a second run from starting if the previous one is still in progress. Monday to Friday includes public holidays, so the job also runs on those days.

Check that it worked

After the first scheduled run, check the log on the VM:

tail -n 20 /var/log/weborion/rebaseline.log

Then check the progress of a job, either in the portal under Batch Jobs → View Batch Jobs, or with Get batch rebaseline job details. Use the numeric API ID from the log, without the RB prefix:

curl -sS -H "Authorization: Bearer $WEBORION_API_TOKEN" \
  https://api.monitor.weborion.io/api/v1/batch_jobs/rebaseline/1234 \
  | jq '[.entries[].status] | group_by(.) | map({(.[0]): length}) | add'

This returns a count of webpages per status, such as {"Completed": 198, "Error": 2}. Each webpage moves through In Queue, Processing, and then Completed or Error.

Customising the script

Rebaseline only webpages with a specific tag

If tags are enabled for your account, you can limit the run to webpages with one tag. Find the tag ID with List tags, then change the list request in the script to use List webpages by tag:

urls_json="$(api "${API_BASE}/api/v1/tags/<tag_id>/urls")"

Change the schedule

Edit the first five fields of the line in /etc/cron.d/weborion-rebaseline. They are minute, hour, day of month, month and day of week.

Schedule	Cron fields
Weekdays at 5:30 PM	`30 17 * * 1-5`
Every day at 6:00 AM	`0 6 * * *`
Mondays at 9:00 AM	`0 9 * * 1`

Troubleshooting

Symptom	Likely cause
`401` from any request	The token is wrong, expired or has been revoked. Generate a new one under Account → Manage Credentials and update `/etc/weborion/rebaseline.env`.
`403` naming a URL ID	The user the token belongs to cannot edit that webpage.
Nothing in the log at 5:30 PM	Check that cron is running (`systemctl status cron`, or `crond` on Amazon Linux) and that the VM timezone is correct (`timedatectl`).
Some webpages show `Error` in the batch job	Those webpages could not be loaded during the rebaseline. Check that they are reachable, then rebaseline them individually from the portal.

For anything else, contact CloudsineAI support.

Getting Started

Configuring Monitoring

Managing Notifications

Managing Changes

Configuring Traffic

API Guide

Getting Support

Scheduled Account Rebaseline

How it works

Before you begin

Setup

Customising the script

Rebaseline only webpages with a specific tag

Change the schedule

Troubleshooting

​How it works

​Before you begin

​Setup

​Customising the script

​Rebaseline only webpages with a specific tag

​Change the schedule

​Troubleshooting

How it works

Before you begin

Setup

Customising the script

Rebaseline only webpages with a specific tag

Change the schedule

Troubleshooting