Scan schedules list and fixed occurrences
Scans API - Scan schedules list
A new endpoint is available to list your scan schedules: recurring scans that run on a set timetable (e.g. daily or weekly).
Endpoint: GET /v1/scans/schedules/
Response include a list of schedules with details such as the schedule name, how often it runs (schedule_period), when the next scan is due (next_scan_date), status (e.g. in progress or scheduled), and options like whether the scan is throttled or limited to web ports. Each schedule also includes the targets and tags it applies to, and the latest scan run (ID, status, start and end times).
For more information, see the API documentation for scan schedules .
Occurrences API - Fixed occurrences
A new endpoint is available to list fixed occurrences: vulnerabilities that have been fixed (remediated). This is separate from the main occurrences list, which includes both open and fixed findings.
Endpoint: GET /v1/occurrences/fixed/
Responses include the same occurrence fields you get from the Issues occurrence list (e.g. affected_host, severity, title, remediated_at, remediation), so you can report on what was fixed and when.
Optional filters
You can narrow results with query parameters:
remediated_after/remediated_before— Limit to occurrences fixed within a date range. Use ISO 8601 format (e.g.2024-01-15T00:00:00Z).severity— One oflow,medium,high, orcritical.target_addresses— Comma-separated target addresses (e.g. hostnames or IPs).tag_names— Comma-separated tag names on the target.
Pagination works the same as other list endpoints (e.g. page, page_size).
For more information, see the API documentation for fixed occurrences.