Scan schedules filtering

Scans API — Filter scan schedules by tag

Scan schedules can now be filtered by tag, so you can pull just the schedules covering a particular part of your estate.

Endpoint: GET /v1/scans/schedules/

• tag_names (optional) — Comma-separated tag names. Returns schedules set to scan any of these tags, as well as schedules that explicitly include a target carrying any of them. Schedules that scan every target are never returned by this filter, since they are not scoped to any specific tag.

Scans API — Filter scan schedules by scope

Scan schedules can now be filtered by whether they cover your whole estate or a specific set of targets and tags.

Endpoint: GET /v1/scans/schedules/

• scan_all_targets (optional) — Set to true to return only schedules that scan every target, or false to return only schedules scoped to specific targets or tags.

Scans API — Scan schedule scope in responses

Each schedule in the scan schedules list now tells you whether it covers every target, so you can tell a whole-estate schedule apart from a scoped one without inspecting its targets and tags.

Endpoint: GET /v1/scans/schedules/

• scan_all_targets — Whether the schedule scans every target. One of: true, false. When true, the targets and target_tags lists are not what determines the schedule's scope.

For more information, see the API documentation for scans.