Reporting and Statistics
The reporting endpoints return the numbers behind the dashboard Overview: open findings, what was found and fixed, coverage problems and SLA status. All are GET requests under https://api.nightviz.ai/api/v1/statistic/. See the API overview for authentication.
All of them need permission to view scans, and results are limited to the projects you can see in the active organization. Several also require that you may view findings in an application, and leave out applications where you may not.
Common notes:
projectnarrows results to the given project ids. Repeat the parameter for more than one. Projects you cannot see add nothing.- Dates (
from,to) are UTC calendar days inYYYY-MM-DDform, inclusive. completein a response isfalsewhen some data was not available to count, so treat the numbers as a floor.- An open finding is any unique finding in an application’s latest completed scan, unless it is marked false positive or won’t fix. Info findings are counted separately from severities in the overview.
- Found and fixed figures are kept current for scans that ended within the last 13 weeks (
data_from). A range that starts earlier is read fromdata_fromon and returnscomplete: false.
Overview
Section titled “Overview”GET /statistic/overview/
Open findings per application, per project and in total, by severity, with a series over time.
Query parameters:
project: project ids.range:30d(daily points),3mor6m(weekly), or12m(monthly). Periods are calendar periods in UTC.
curl -H "Authorization: Token $NIGHTVISION_TOKEN" \ "https://api.nightviz.ai/api/v1/statistic/overview/?range=30d"{ "complete": true, "range": "30d", "granularity": "day", "totals": {"critical": 1, "high": 4, "medium": 9, "low": 12, "info": 3, "total": 29}, "applications": [ { "target_id": "00000000-0000-4000-8000-000000000010", "target_name": "payments-api", "target_type": "URL", "project_id": "00000000-0000-4000-8000-000000000040", "project_name": "Payments", "latest_scan_id": "00000000-0000-4000-8000-000000000060", "latest_scan_ended_at": "2026-03-01T08:00:00Z", "latest_scan_session": "signed_in", "latest_scan_credentials_id": null, "latest_login_check": null, "own_counts": {"critical": 1, "high": 4, "medium": 9, "low": 12, "info": 3, "total": 29}, "source_repository": null, "counts": {"critical": 1, "high": 4, "medium": 9, "low": 12, "info": 3, "total": 29} } ], "projects": [ { "project_id": "00000000-0000-4000-8000-000000000040", "project_name": "Payments", "applications": 1, "counts": {"critical": 1, "high": 4, "medium": 9, "low": 12, "info": 3, "total": 29}, "never_scanned": 0, "stale": 0, "signed_out": 0, "no_authentication": 1 } ], "series": [ {"critical": 1, "high": 4, "medium": 9, "low": 12, "info": 3, "total": 29, "period_start": "2026-03-01"} ]}latest_scan_session is signed_in, anonymous, login_failed or unverified. The example trims the series to one point.
Open issues
Section titled “Open issues”GET /statistic/open-issues/
The Overview’s open findings, one row per application and check, worst first. Paginated.
Query parameters:
project,target: project or application ids.severity: one or more ofINFO,LOW,MEDIUM,HIGH,CRITICAL(any case).resolution: one or more of0(open),1(resolved),2(false positive),4(won’t fix). Default: open and resolved.assignee: a user id,me, ornone.overdue:truefor only findings that are overdue under your SLA policy.search: matches the check name or the application name.page,page_size
curl -H "Authorization: Token $NIGHTVISION_TOKEN" \ "https://api.nightviz.ai/api/v1/statistic/open-issues/?severity=CRITICAL&severity=HIGH&assignee=none"{ "count": 1, "next": null, "previous": null, "results": [ { "target_id": "00000000-0000-4000-8000-000000000010", "target_name": "payments-api", "project_id": "00000000-0000-4000-8000-000000000040", "project_name": "Payments", "scan_id": "00000000-0000-4000-8000-000000000060", "kind_id": 101, "nuclei_template_id": null, "name": "SQL Injection", "severity": "HIGH", "instance_count": 3, "new_instance_count": 1, "first_issue_id": "00000000-0000-4000-8000-000000000050", "first_seen_at": "2026-02-01T08:00:00Z", "owner": {"kind": "group", "id": "00000000-0000-4000-8000-000000000020", "name": "Platform"}, "assignee": null, "jira_issue_key": null, "jira_status": null, "jira_status_category": null, "not_retested_in_scan_id": null, "not_retested_reason": null } ]}owner.kind is user or group. When a finding could not be retested in the latest scan, not_retested_reason says why (for example signed_out, login_failed, endpoint_not_requested or check_not_run).
Found and fixed
Section titled “Found and fixed”GET /statistic/found-fixed/
Unique findings found (new) and fixed (resolved) per ISO week or month. Info is excluded. Marking a finding resolved is not a fix; a finding counts as fixed only when a later scan could have found it again and did not.
Query parameters:
project: project ids.from,to: the range. With none offrom,toandbucket, the last 12 weeks.bucket:week(default) ormonth.
curl -H "Authorization: Token $NIGHTVISION_TOKEN" \ "https://api.nightviz.ai/api/v1/statistic/found-fixed/?bucket=week"{ "as_of": "2026-03-02T10:00:00Z", "complete": true, "bucket": "week", "from": "2026-01-12", "to": "2026-03-02", "data_from": "2025-12-01", "weeks": [ {"week_start": "2026-02-23", "start": "2026-02-23", "end": "2026-03-01", "new": 5, "resolved": 3} ]}Fixed findings
Section titled “Fixed findings”GET /statistic/fixed-findings/
Every finding fixed in a period, one row each, oldest fix first. Paginated with page (default 1) and page_size (default 500, up to 1000); next_page in the response is the next page number or null.
Query parameters:
project: project ids.severity: severities to include (any case). Info is never listed.page,page_sizefrom,to: the period. Send both when reading several pages so every page reads the same period.
curl -H "Authorization: Token $NIGHTVISION_TOKEN" \ "https://api.nightviz.ai/api/v1/statistic/fixed-findings/?from=2026-02-01&to=2026-02-28"{ "as_of": "2026-03-02T10:00:00Z", "from": "2026-02-01", "to": "2026-02-28", "data_from": "2025-12-01", "complete": true, "count": 1, "marked_resolved_count": 0, "truncated": false, "max_rows": 20000, "page": 1, "page_size": 500, "next_page": null, "results": [ { "issue_id": "00000000-0000-4000-8000-000000000050", "issue_scan_id": "00000000-0000-4000-8000-000000000061", "name": "SQL Injection", "kind_id": 101, "nuclei_template_id": null, "severity": "HIGH", "target_id": "00000000-0000-4000-8000-000000000010", "target_name": "payments-api", "project_id": "00000000-0000-4000-8000-000000000040", "project_name": "Payments", "http_method": "GET", "url_path": "/api/orders", "parameter_name": "id", "first_seen_at": "2026-02-01T08:00:00Z", "redetected_at": null, "fixed_at": "2026-02-10T08:00:00Z", "fixing_scan_id": "00000000-0000-4000-8000-000000000062", "days_to_fix": 9.0, "came_back": false, "current_mark": "open" } ]}truncated is true when count is above max_rows; narrow the period or filters to read the rest.
Needs attention
Section titled “Needs attention”GET /statistic/needs-attention/
Coverage problems that make the Overview’s counts less reliable, worst kind first. Returns a JSON array, not a paginated object. Query parameter: project. Organization-level items (discovery_unowned) appear only when no project is given.
curl -H "Authorization: Token $NIGHTVISION_TOKEN" \ https://api.nightviz.ai/api/v1/statistic/needs-attention/[ { "type": "stale", "target_id": "00000000-0000-4000-8000-000000000010", "target_name": "payments-api", "project_id": "00000000-0000-4000-8000-000000000040", "project_name": "Payments", "link": {"kind": "target", "id": "00000000-0000-4000-8000-000000000010"}, "last_scanned_at": "2026-02-01T08:00:00Z" }]type is one of:
login_failing: the latest login attempt in the last 30 days did not succeed.scan_failed: the most recent run failed, timed out or was aborted, and is newer than the latest completed scan.scan_blocked: the latest completed scan was disrupted.signed_out: the application has a login, but its latest completed scan ran signed out or unverified.no_authentication: the application has no credentials.stale: no completed scan in the last 14 days.never_scanned: no completed scan at all.unscheduled: no enabled schedule.discovery_unowned: live hosts ranked critical that no target covers.
Other fields (such as scan_id, session, status, ended_at, root_domain) appear on the types they apply to.
GET /statistic/sla/
Service-level numbers for open findings: how many are overdue against your SLA policy, the oldest open critical, mean time to fix and findings fixed after their time ran out. Info is left out.
Query parameters:
project: project ids.from,to,bucket(weekormonth): read mean time to fix over a range, split into buckets, instead of the default last 90 days. Open and overdue numbers are always as of now.
curl -H "Authorization: Token $NIGHTVISION_TOKEN" \ https://api.nightviz.ai/api/v1/statistic/sla/{ "as_of": "2026-03-02T10:00:00Z", "policy": { "critical_days": 7, "high_days": 30, "medium_days": 90, "low_days": 180, "is_default": false, "updated_by": null, "updated_at": null }, "open": {"critical": 1, "high": 4, "medium": 9, "low": 12}, "overdue": {"critical": 1, "high": 2, "medium": 0, "low": 0, "total": 3}, "oldest_open_critical": { "issue_id": "00000000-0000-4000-8000-000000000050", "scan_id": "00000000-0000-4000-8000-000000000060", "kind_id": 101, "nuclei_template_id": null, "name": "SQL Injection", "target_id": "00000000-0000-4000-8000-000000000010", "target_name": "payments-api", "first_seen_at": "2026-02-01T08:00:00Z", "age_days": 29 }, "mttr_days": { "critical": 4.5, "high": 12.0, "medium": null, "low": null, "all": 9.2, "fixed_count": 6, "fixed_by_severity": {"critical": 1, "high": 3, "medium": 2, "low": 0}, "window_days": 90 }, "fixed_late_90d": 1, "by_project": [ {"project_id": "00000000-0000-4000-8000-000000000040", "overdue_total": 3} ], "complete": true}When you pass from, to or bucket, the response also includes bucket, from, to, data_from and a buckets array, where each entry has start, end and an mttr_days object in the shape above. A finding with no first-seen date is open but never overdue, and sets complete to false.