Triage a finding

PATCH 
/api/v1/findings/:finding_id

Update finding triage (status, severity, fix suggestion, etc).

Accepts a finding public code (e.g., AIS-ADB-TLP-001). If the request changes status, a silent debounced report regeneration is enqueued for the active report of the same assessment (30s window).

• Scope required: findings:triage.
• Rate-limit tier: read/default (no dedicated mutation rate-limit).
• Side-effects: may enqueue the background task queue silent_regenerate_report_task.
• Idempotent per-request; repeated identical payloads are safe.

Request

Responses

200

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.