Currently-open findings past their severity SLA, worst overage first
GET/api/v1/findings/stats/sla-breaches
Open findings exceeding the org's per-severity remediation SLA.
The actionable companion to /stats/remediation: each row carries the
finding, its days-open, the SLA it broke, and the overage. Severities with
no SLA in Organization.sla_policy are skipped. Sorted worst-overage
first.
- Scope required:
findings:read. - Response supports ETag revalidation (304 Not Modified).
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 422
- 429
- 500
Successful Response
Bad request — malformed input or failed validation.
Missing, expired, or invalid credentials.
Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.
Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).
Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).
Semantic validation failure — request shape was valid but contents were not.
Too many requests — rate limited. Retry after the window resets.
Internal server error — unexpected failure.