Retest all findings
Starts retest scans for the findings of the scan. A single finding gets one targeted retest scan. Several findings share retest scans: one scan per group of up to 50 findings, in which every finding is checked by its own agent, all in parallel. The request checks access, the findings in scope, and the replacement uploads. Then it answers with status 202 and creates the retest scans in the background. The retest scans do not appear in the scan list. Read them, and the launches that are still starting or that failed to start, through GET /scans/{scanId}/retests on the source scan. A finding with a retest that is still running is skipped.
Authorizations
API token obtained from the Tokens endpoint or CLI device login. Include as Authorization: Bearer <token>. Requests made with a managed CLI session also include X-Strix-Workspace: <organization_id> to pin a process to the workspace it started in; recovery endpoints report the current workspace after a concurrent switch.
Path Parameters
UUID of the scan. Use the id field of a scan from listScans.
Body
Response
No retest started. Every finding in scope is already retesting, or the scope has no findings.
The batch that starts the retests. The value is null when no retest was accepted.
The number of retests that are starting in the background.
The number of findings in the requested scope.
The number of findings that the request skipped because a retest of the finding is still running or starting.