Skip to main content
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: write

Authorizations

X-Api-Key
string
header
required

Path Parameters

id
string
required

Body

application/json
state
enum<string>

New finding state

Available options:
open,
true_positive,
false_positive,
accepted_risk,
resolved,
closed
severity
enum<string>

New severity level

Available options:
critical,
high,
medium,
low,
info
state_reason
string

Reason for the state change (defaults to reason if omitted)

severity_reason
string

Reason for the severity change (defaults to reason if omitted)

reason
string

Shorthand reason applied to both state and severity changes when their specific reason is not provided

duplicate_of
string | null

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
id
string
required
state
enum<string>
required
Available options:
open,
true_positive,
false_positive,
accepted_risk,
resolved,
closed
severity
enum<string>
required
Available options:
critical,
high,
medium,
low,
info
duplicate_of
string | null
required

UUID of the canonical finding this duplicates, if any.