API reference

Monitoring

Configure how often a verified site is rescanned and which changes raise alerts. Monitoring requires a verified domain.

PUT/v1/sites/{id}/monitoring

GET/v1/monitoring

Update a site's monitoring

Field	Type	Status	Description
active	boolean	required	Turn recurring rescans on or off.
frequency	string	optional	weekly (Starter) or daily (Practice+).
plan	string	optional	The monitoring plan governing quota and cadence options.

json

{ "active": true, "frequency": "daily" }

Examples

# Enable daily monitoring on a verified site
curl -s -X PUT https://api.sifthealth.app/v1/sites/site_a1b2/monitoring \
  -H "Authorization: Bearer $SIFT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"active": true, "frequency": "daily"}'

# List all monitoring subscriptions
curl -s https://api.sifthealth.app/v1/monitoring \
  -H "Authorization: Bearer $SIFT_API_KEY"

Alerts ride on monitoring

Each scheduled rescan diffs against the baseline and emits alerts — new_finding, resolved_finding, score_drop, cert_expiring. Tune which fire in the dashboard; see the alerts guide.

Continuous monitoring

The end-to-end setup.

Configure alerts

Pick which events notify you.

Verify a site

Required before monitoring.

Internal cron

How due scans get run.