Get issue detail
Get detailed information about a specific issue.
Path Parameters
Issue ID
Response
Issue detail
confirmed, firm, tentative Email of the user who created this issue
critical, high, medium, low, none critical, high, medium, low, info, unknown Source of the issue (e.g. nuclei, agent, burp, snyk, manual, etc.)
out_of_scope is reserved and no issue uses it; creating or editing an issue with it is refused.
unverified, open, confirmed, in_progress, resolved, false_positive, accepted_risk, duplicate, out_of_scope vulnerability, misconfiguration, exposure, information, compliance, other Populated on detail view (GET /issues/:id). NULL on list view.
Number of affected assets tracked for the issue.
CVSS score 0.0-10.0 as string (numeric)
Root domain of the host, for example example.com for www.example.com.
Version of the structured evidence item format. Supported value is 1.
1 Reason this issue was marked as false positive.
Content-stable hash for cross-run dedup. Server matches (source, ticket_id, fingerprint) tuple on bulk insert.
Business and technical impact of the finding.
When the issue was last observed or re-confirmed by a scan.
Project this issue belongs to (null = personal/unscoped).
Actionable remediation guidance.
Ordered steps to reproduce the finding.
Reason the risk was accepted.
Human-readable sequential identifier (e.g. ISSUE-1, ISSUE-2). Auto-assigned on creation.
"ISSUE-42"
Returned when an edit changed a PD Cloud-owned field (status, severity, ticket, delete) of a synced finding. Each PD Cloud step is reported; synced is false when Neo could not read PD Cloud's resulting state yet (it arrives shortly through the sync), and the issue returned is then Neo's earlier copy.
What is affected (host, ARN, app, file:line, etc.)
Category of target (host, cloud_resource, app, code, container, dependency, api, certificate)
External ticket ID or key.
Link to external ticket (Jira, Linear, GitHub issue, etc.)

