Update finding state, severity, and/or duplicate link
Findings
Update finding
Change a finding’s state, severity, and/or duplicate link.
PATCH
Update finding state, severity, and/or duplicate link
Updates the
state, severity, duplicate_of, or any combination of them on a single finding. Every change is recorded to the finding’s audit trail and propagated to connected integrations (GitHub, Slack, Jira, Linear).
Scope required:
writeAuthorizations
Path Parameters
Body
application/json
New finding state
Available options:
open, true_positive, false_positive, accepted_risk, resolved, closed New severity level
Available options:
critical, high, medium, low, info Reason for the state change (defaults to reason if omitted)
Reason for the severity change (defaults to reason if omitted)
Shorthand reason applied to both state and severity changes when their specific reason is not provided
UUID of the canonical finding to mark this finding as a duplicate of, or null to unmark. The target must be in the same repository.
Response
200 - application/json
Available options:
open, true_positive, false_positive, accepted_risk, resolved, closed Available options:
critical, high, medium, low, info UUID of the canonical finding this duplicates, if any.