Monitors

Page-change monitor operations

First-capture behavior is the same for both monitor types: the first capture is a silent baseline (has_change: false, change_pct: null) with no change_detected webhook, whether the monitor is scrape or screenshot. From the second capture onward both types diff against the previous capture.

monitors › captures

Monitor capture sub-resources

Option	Description
`-h, --help`	display help for command

monitors › captures › list

List captures for a monitor

Option	Description
`-h, --help`	display help for command

$ bytekit monitors captures list <id>

monitors › create

Create a page-change monitor

Option	Description
`--url <url>`	URL to monitor
`--interval-type <type>`	Check interval: hourly, daily, weekly, or cron
`--webhook-url <url>`	HTTPS webhook URL notified on change
`--cron <expr>`	Cron expression (required when --interval-type is
`-h, --help`	display help for command

$ bytekit monitors create --url <url> --interval-type <type> --webhook-url <url> --cron <expr>

monitors › list

List all monitors

Option	Description
`-h, --help`	display help for command

$ bytekit monitors list

monitors › get

Get a monitor by ID

Option	Description
`-h, --help`	display help for command

$ bytekit monitors get <id>

monitors › update

Update a monitor

Option	Description
`--interval-type <type>`	New check interval: hourly, daily, weekly, or cron
`--cron <expr>`	New cron expression (when interval-type is cron, e.g.
`--webhook-url <url>`	New HTTPS webhook URL
`-h, --help`	display help for command

$ bytekit monitors update <id> --interval-type <type> --cron <expr> --webhook-url <url>

monitors › delete

Delete a monitor

Option	Description
`-h, --help`	display help for command

$ bytekit monitors delete <id>