code-scan

Create Code Scan Exclusion

Add an exclusion rule (Developer+, same gate as code-scan ingest).

IDEMPOTENT: a re-POST of the same (type, value) returns the EXISTING rule with a 200 — never a duplicate, never a 409. Persistent: the rule survives re-scans because it matches by value/path, not by fingerprint.

post/v1/projects/{project_id}/code-scan/exclusions

Request

  • Base URL: https://api.sonenta.dev
  • URL: https://api.sonenta.dev/v1/projects/{project_id}/code-scan/exclusions
  • Auth: none declared

Path parameters

project_idstring required

Request body

type'string' | 'file' | 'folder' required

Granularity: string matches finding.string == value · file matches finding.file == value · folder matches finding.file under value + '/'.

valuestring required

Exact value/path (repo-relative POSIX). A folder prefix is normalised WITHOUT a trailing slash, so src/ui and src/ui/ are the same rule.

notestring nullable

Optional free-text reason shown in the management view.

Response

Successful Response

uuidstring required
typestring required
valuestring required
notestring nullable
created_atstring date-time required
matched_countinteger required

Findings this ONE rule masks right now, ALL statuses. Rules can overlap, so the sum across rules is not the project total — that is summary.excluded.

Changes

No recorded changes to this operation across all 1 revision of this API.