Findings

Unified security findings aggregated from all scanners.

📄️ List Findings

Return a cursor-paginated collection of findings for the authenticated client, supporting query-string filters, sorting, field selection, and a finding_type selector. Users with the developer role only see findings assigned to them.

📄️ Get Facet Values For A Field

Return the distinct values (with live counts) of a facetable finding field, scoped to the current typed query (fq) and optional search prefix. Powers the filter UI's autocompletes, checklists and range histograms.

📄️ Get Batched Ad-Hoc Condition Counts

Return the count of findings matching each named ad-hoc condition in `targets`, scoped to the current typed query (fq) and legacy filters[...] scope — all in one Mongo round trip. Powers the TRIAGE shortcut chips (Reachable, EPSS, Vulnerability, New 7d) without a separate findings-list request per chip.

📄️ Convert Natural Language To A Findings Filter

LLM-powered conversion of a natural-language request into a validated fq clause list. The field catalog is generated from the live query registry, and the output is re-validated fail-closed before being returned. Metered by the monthly ai_filter_conversions quota.

📄️ Get Finding Selected Columns

Return the default finding table columns together with the columns the authenticated user has selected for the findings view.

📄️ Save Finding Selected Columns

Persist the authenticated user's selected finding table columns and return the defaults alongside the saved selection.

📄️ Bulk Send Findings to Developers

Assign multiple findings to the given developer IDs and mark them as ready for review. Returns a 207 multi-status response with a per-finding result; returns 403 when the user is not in the organization and 400 for invalid finding IDs.

📄️ Generate Bulk AI Remediations

Request AI remediation generation for multiple findings at once. Findings are grouped by repository server-side, producing one remediation (and optionally one pull request) per repository instead of one per finding. Responds 207 with a per-finding status list: 202 when dispatch was accepted, 404 when the finding does not exist, and 409 when a remediation already exists for it. The response includes a bulk_run_id that can be polled via GET /remediations/bulk-runs/{run_id}. Requests above the batch limit are rejected with 422.

📄️ List Bulk Remediation Runs

Return a paginated list of the client's bulk remediation runs (Bulk Remediation Control Center), sorted by `created_at` descending. `status` filters on the run's stored status (running, completed, or incomplete when finalized by the sweep after prolonged inactivity). A bulk run is finding-driven and can span multiple repositories, so there is no repository_id filter — see GET /remediations/bulk-runs/{run_id} to fetch a single known run.

📄️ Get Bulk Remediation Run

Return the progress document of a bulk remediation run: total findings, per-finding completion/failure lists, and overall status (running, completed, or incomplete when finalized by the sweep after prolonged inactivity).

📄️ Findings by Repository Chart

Return open finding counts grouped by enriched repository for the authenticated client, limited to max_repos entries. The finding_type query parameter (app, scm, cloud or all) selects which tool families are counted.

📄️ Findings by Language and Severity

Return open finding counts grouped by programming language and severity (Low, Medium, High, Critical). The top four languages are listed individually and the remainder are aggregated under 'Other'.

📄️ Upload Scan Results

Execute the UploadScan workflow that ingests externally produced scan results for the given repository using the caller's bearer token.

📄️ Download Pentest Report

Download the markdown penetration test report generated by the pentest engine for the given scan request. Returns 404 when the scan or its report is not available.

📄️ Apply Bulk Remediation Actions

Dispatch pull request or issue creation workflows for each remediation ID in the request body. Returns a 207 multi-status response with per-item results: 202 accepted, 404 not found, 409 already in a terminal status, or 422 for an unknown remediation type.

📄️ Download JSON Findings

Export findings as a SARIF JSON document. By default only enriched findings are included; pass filters[include_all]=true to export every finding for the requested repository, including duplicates and false positives.

📄️ Generate PDF Findings Report

Create a report job and trigger asynchronous PDF generation for the currently filtered findings. Returns 201 with a job ID and Location header; the user is emailed when the report is ready. Limited to 5 report requests per hour (429 when exceeded). Requires the report_pdf plan feature (Scale+).

📄️ Generate PDF for Single Finding

Create a report job and trigger asynchronous PDF generation for a single finding brief. Returns 201 with a job ID and Location header; the user is emailed when the report is ready. Limited to 5 report requests per hour (429 when exceeded).