How do I get the new, fixed and regressed findings for a scan through the API?

Steps

1. Find the ID of the scan. A CI trigger returns it as scanId.
2. Send your Bearer token with the request.
3. Call GET /api/scans/:id/diff. It needs scan:read.
4. Read the three groups the route is built around: new, fixed and regressed findings.
5. Look at regressions first: these are issues that you fixed before and that have come back.

Good to know

The reference describes the route as a diff of findings against the target's history. The Diff tab on the scan detail page shows the same idea in the app, comparing with the previous completed scan of the target. On the very first scan, the tab says "No previous scan to compare against.", so expect little or nothing from the API in that case too.

The lifecycle behind it is simple. Issues persist per target. A later scan that no longer finds one marks it fixed. If it reappears, Cyberlop flags a regression instead of a fresh finding.

This route helps most in pipelines. After a merge, ask for the diff and look only at what is new. That keeps the noise down and puts the focus on the change you just shipped. Field names are not listed on the page, so read the downloaded OpenAPI spec for field names before you parse it.

For the in-app version, read how to compare scans with the Diff tab. To list every finding of a scan instead, see how to pull the findings for one scan.

Related questions

• How do I pull the findings for one scan through the API?
• How do I check a CI-triggered scan's result through the API?
• How do I find findings that came back after being fixed?
• How do I download the API spec?
• How do I get the Dashboard numbers through the API?

Full tutorial

How to compare scans in Cyberlop with the Diff tab

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre