Scheduled Scans — Shieldome Docs

What are scheduled scans?

Scheduled scans automatically run at a set interval without any manual action. They are useful for:

Continuous security monitoring of production sites
Detecting new vulnerabilities introduced by updates or configuration changes
Generating regular compliance evidence
Tracking security posture improvements over time

🪙

Token cost: Each scheduled run consumes 1 scan token, the same as a manual scan. Make sure your account has enough tokens to cover your schedule frequency. A daily scan uses ~30 tokens per month.

Creating a scheduled scan

From the dashboard

Open the Scheduled tab in the dashboard
Click New Schedule
Enter the target URL and scan type
Choose an interval: Hourly, Daily, Weekly, or Monthly
Click Save

Via API

bash

curl -X POST \
  -H "X-Shieldome-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url":            "https://example.com",
    "scan_type":      "both",
    "interval_hours": 24
  }' \
  https://yourdomain.com/api/schedules

Supported intervals

Interval	`interval_hours` value	Use case
Hourly	`1`	High-change environments, active development
Daily	`24`	Most production sites — recommended default
Weekly	`168`	Lower-traffic sites, supplement to manual scans
Monthly	`720`	Compliance evidence, infrequently updated sites

Managing schedules

List all schedules

bash

curl -H "X-Shieldome-Key: YOUR_API_KEY" \
  https://yourdomain.com/api/schedules

Delete a schedule

bash

curl -X DELETE \
  -H "X-Shieldome-Key: YOUR_API_KEY" \
  https://yourdomain.com/api/schedules/{schedule_id}

Scan history from scheduled runs

Every scheduled scan run creates a regular scan entry in your history, indistinguishable from manually triggered scans. You can compare runs over time using the Trends chart in the History tab.

Trends chart

The Trends chart plots the risk score and finding counts across your most recent scans for a given target. It shows:

Risk score over time — rises when new vulnerabilities appear, drops when they are resolved
Finding counts by severity — separate lines for critical, high, medium, and low
Time range — the last 30 scans for the selected target (or all scans if fewer than 30)

To view the Trends chart: open the History tab, filter by a specific target URL, then click Show Trends. Spikes in the chart indicate when new issues were introduced; dips indicate remediation.

ℹ️

The Trends chart is most useful when the same URL is scanned on a recurring schedule. Ad-hoc scans of different targets on the same account appear in the chart only if you filter by URL.

💡

Pro tip: Tag your scheduled scans (e.g. production, weekly-audit) to filter them easily in the History tab.

Webhook notifications

Attach a webhook URL to any scheduled scan so you receive a POST request the moment the scan completes. The payload is the same JSON structure as the scan detail endpoint:

json — webhook payload

{
  "scan_id":     "a1b2c3d4-...",
  "target_url":  "https://example.com",
  "status":      "completed",
  "summary": {
    "risk_score": 35,
    "critical": 0, "high": 1, "medium": 3
  },
  "new_findings": [/* findings not present in the previous scan */]
}

Set the webhook URL in the scheduled scan settings or via the API: include "webhook_url": "https://your-server.com/hook" in the POST /api/scan body.

Weekly digest emails

SaaS monitoring subscribers automatically receive a weekly digest email every Monday summarizing:

New findings detected since the previous week's scan
Findings that were resolved (no longer present)
Risk score trend (up/down/stable)
A link to the full scan report

You can configure digest frequency and disable it per domain in the Monitoring settings panel.