Recurring finding rollup across a project's assessments

GET 
/api/v1/projects/:project_id/findings/recurring

Group project findings by runner root-cause fingerprint.

The underlying collector is assessment-RBAC aware, so groups never include an occurrence from an assessment the caller cannot see. Findings without a fingerprint stay visible as singleton groups keyed by their public id.

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.