Findings, History and SLA Policy
Assign findings to people, read a finding’s history, and read or set the organization’s SLA policy. Base URL: https://api.nightviz.ai/api/v1/. See the API overview for authentication.
Assign a finding
Section titled “Assign a finding”POST /issues/{id}/assign/
Assigns the finding to a person, or clears the assignment. The assignment belongs to the finding, so it stays in place across scans. The assignee must be an active member of the application’s organization. Needs permission to change findings.
Request body: assignee_id, a user id or null to clear.
curl -X POST -H "Authorization: Token $NIGHTVISION_TOKEN" \ -H "Content-Type: application/json" \ -d '{"assignee_id": "00000000-0000-4000-8000-000000000030"}' \ https://api.nightviz.ai/api/v1/issues/00000000-0000-4000-8000-000000000050/assign/{ "assignee": { "id": "00000000-0000-4000-8000-000000000030", "name": "Alex Example", "email": "alex@example.com" }}assignee is null after clearing.
List possible assignees
Section titled “List possible assignees”GET /issues/{id}/assignee-candidates/
Returns the people the finding can be assigned to, which is exactly what assign accepts. Query parameters: search (matches first name, last name, email or username), page, page_size. Results use the same id, name, email shape as above, in the usual paginated envelope. Needs permission to change findings.
curl -H "Authorization: Token $NIGHTVISION_TOKEN" \ "https://api.nightviz.ai/api/v1/issues/00000000-0000-4000-8000-000000000050/assignee-candidates/?search=alex"Finding history
Section titled “Finding history”GET /issues/{id}/history/
Returns the finding’s history, newest first, up to 200 events: when it was detected or fixed, every status change with its reason, review date and actor, and every assignment. The history answers for the finding itself, whichever scan’s row you ask about.
curl -H "Authorization: Token $NIGHTVISION_TOKEN" \ https://api.nightviz.ai/api/v1/issues/00000000-0000-4000-8000-000000000050/history/{ "events": [ { "type": "status", "at": "2026-02-03T09:30:00Z", "from": "open", "to": "false_positive", "reason": "Input is validated upstream.", "review_by": "2026-05-03", "actor": { "id": "00000000-0000-4000-8000-000000000030", "name": "Alex Example" }, "source": "user", "scan_id": "00000000-0000-4000-8000-000000000060", "previous_scan_id": null, "issue_id": "00000000-0000-4000-8000-000000000050", "first": false, "assignee": null } ], "complete": true}type:detected,fixed,not_retested,statusorassigned.fromandto(status changes):open,resolved,false_positiveorwont_fix.source:user,jiraorsystem.complete: whether the list covers the finding’s whole history.
Needs permission to view findings.
SLA policy
Section titled “SLA policy”The SLA policy sets how many days an open finding of each severity may stay open, counted from when it was first seen.
Read the policy
Section titled “Read the policy”GET /organization/sla-policy/
Readable by any active member of the organization.
curl -H "Authorization: Token $NIGHTVISION_TOKEN" \ https://api.nightviz.ai/api/v1/organization/sla-policy/{ "critical_days": 7, "high_days": 30, "medium_days": 90, "low_days": 180, "is_default": false, "updated_by": "00000000-0000-4000-8000-000000000030", "updated_at": "2026-01-20T12:00:00Z"}is_default is true until an administrator saves a policy.
Save the policy
Section titled “Save the policy”PUT /organization/sla-policy/
Sets the policy for the active organization. Each of critical_days, high_days, medium_days and low_days is required, from 1 to 3650. Needs permission to manage organization settings. The response has the same shape as the read.
curl -X PUT -H "Authorization: Token $NIGHTVISION_TOKEN" \ -H "Content-Type: application/json" \ -d '{"critical_days": 7, "high_days": 30, "medium_days": 90, "low_days": 180}' \ https://api.nightviz.ai/api/v1/organization/sla-policy/To see how many findings are overdue under this policy, use GET /statistic/sla/.