> ## Documentation Index > Fetch the complete documentation index at: https://docs.app.strix.ai/llms.txt > Use this file to discover all available pages before exploring further. # List scan retests > Lists the newest retest of each finding of this scan, with progress counts. ## OpenAPI ````yaml /openapi.json get /scans/{scanId}/retests openapi: 3.1.0 info: title: Strix API version: 1.0.0 description: >- Public REST API for the Strix autonomous penetration testing platform. Manage scans, vulnerabilities, assets, schedules, API tokens, and webhooks. servers: - url: /api/v1 description: Strix v1 API security: - BearerAuth: [] tags: - name: Scans description: Launch, monitor, and manage security scans. - name: Vulnerabilities description: View and triage discovered vulnerabilities. - name: Assets description: Domains and repositories registered for scanning. - name: Schedules description: Recurring scan schedules (Pro plan). - name: Search description: Search across issues, pentests, PR reviews, chats, assets and schedules. - name: Tokens description: Manage API tokens for authentication. - name: Webhooks description: Configure webhook subscriptions for real-time event notifications. - name: Organization description: Workspace configuration for the authenticated organization. - name: Members description: Manage organization members and roles. - name: Invitations description: List and revoke organization invitations. - name: PR Reviews description: Automated security review of pull requests. - name: Connectors description: Network connectors for scanning internal/private targets. - name: Knowledge description: >- Organization knowledge base: documents, policies, and repo profiles that steer the agent. - name: Uploads description: Upload source/code/documentation archives for whitebox scans. - name: Integrations description: Third-party integrations (GitLab, Bitbucket, ticketing). - name: Chat description: Conversational agent sessions. - name: Analytics description: Aggregate dashboard analytics. - name: Test Users description: >- Per-domain test accounts (with optional MFA) the agent authenticates as during scans. - name: License description: Self-hosted license state, entitlements, and aggregate usage. - name: Supply Chain description: >- SBOM inventory, supply-chain findings, scans, and policy for connected repositories. - name: CLI description: >- Device authorization endpoints that let the Strix CLI and coding agents sign in and receive an API token. - name: Billing description: Credit balance, agent-payable top-ups, and automatic top-up settings. - name: Workspaces description: List, create, and switch workspaces. - name: Asset Discovery description: >- Passive reconnaissance runs that map the organization's external attack surface, and the discovered-asset inventory they fill. - name: Containers description: >- Container registries, tracked images, image scans, findings, and SBOM components. - name: Run Logs description: Persisted engine logs and the diagnostics bundle of a self-hosted install. paths: /scans/{scanId}/retests: get: tags: - Scans summary: List scan retests description: >- Lists the newest retest of each finding of this scan, with progress counts. operationId: listScanRetests parameters: - $ref: '#/components/parameters/ScanId' responses: '200': description: Retest runs. content: application/json: schema: $ref: '#/components/schemas/ScanRetests' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '500': $ref: '#/components/responses/InternalError' security: - BearerAuth: - scans:read components: parameters: ScanId: description: UUID of the scan. Use the `id` field of a scan from `listScans`. name: scanId in: path required: true schema: type: string format: uuid schemas: ScanRetests: type: object properties: runs: type: array items: $ref: '#/components/schemas/ScanRetestRun' total: type: integer completed: type: integer description: Runs with the status completed, failed, or cancelled. running: type: integer description: Runs that are pending or running. launches: type: array description: >- Retests that `POST /scans/{scanId}/retest-all` accepted but that have no retest scan yet. A launch leaves this list when its retest scan appears in `runs`. items: $ref: '#/components/schemas/ScanRetestLaunch' starting: type: integer description: Launches that are still starting. failed_to_start: type: integer description: >- Launches that did not start. Send `POST /scans/{scanId}/retest-all` again to retry them. launch_progress: type: - object - 'null' description: >- Progress of the batches that are still starting. The value is null when no batch is starting. properties: requested: type: integer description: Retests that the batches accepted. settled: type: integer description: >- Retests of the batches that have a retest scan or that failed to start. required: - requested - settled required: - runs - total - completed - running - launches - starting - failed_to_start - launch_progress ScanRetestRun: type: object description: The newest retest of one finding of the scan. properties: vulnerability_id: type: string description: >- The finding the retest checks. This is always the original finding, also when the scan is itself a retest that observed the finding again. title: type: string severity: $ref: '#/components/schemas/VulnerabilitySeverity' issue_status: $ref: '#/components/schemas/VulnerabilityStatus' description: >- The current triage status of the finding. It can change after the retest ran. retest_scan_id: type: string description: The retest scan. Read it with `GET /scans/{scanId}`. retest_status: $ref: '#/components/schemas/ScanStatus' retest_stop_reason: type: - string - 'null' enum: - budget_exceeded - rate_limited - agents_incomplete - null description: >- Why the engine ended the retest before its agents finished. Null when the agents finished on their own. An `inconclusive` outcome with a stop reason means the retest did not check the finding, not that the target was unreachable. outcome: $ref: '#/components/schemas/RetestOutcome' description: >- What the retest found. It does not change with later triage of the finding. inconclusive_reason: type: - string - 'null' description: >- Why an `inconclusive` retest could not verify the finding, in the retest agent's words (for example, a test credential no longer authenticates). Null for every other outcome, and when the retest gave no reason; the retest scan's trace has the details. created_at: type: string format: date-time required: - vulnerability_id - title - severity - issue_status - retest_scan_id - retest_status - retest_stop_reason - outcome - inconclusive_reason - created_at ScanRetestLaunch: type: object properties: vulnerability_id: type: string description: The issue that the retest targets. title: type: string severity: $ref: '#/components/schemas/VulnerabilitySeverity' status: type: string enum: - starting - failed error: type: - string - 'null' description: >- Why the retest did not start. The value is null while the retest is starting. requested_at: type: string format: date-time upload_ids: type: - array - 'null' items: type: string description: >- The replacement uploads of the request. The value is null when the request had none. required: - vulnerability_id - title - severity - status - error - requested_at - upload_ids ErrorResponse: type: object properties: detail: type: string description: Human-readable explanation of the error. code: type: string description: >- Stable machine-readable error code. `insufficient_scope` means the token does not hold the scope that this endpoint requires. required_scope: $ref: '#/components/schemas/ApiV1Scope' description: >- Scope that the caller must add to the token. Returned with the `insufficient_scope` code. docs: type: string format: uri description: Documentation page that explains how to resolve the error. hint: type: string description: >- One instruction that resolves the error. For `insufficient_scope`, a CLI session gets the `strix cloud session scopes set full` or `strix cloud login --scope-profile full` command, and an API token gets the settings page where the user creates a token with the scope. When the owner's role cannot hold the scope, the hint asks for a role change instead. required: - detail VulnerabilitySeverity: type: string enum: - critical - high - medium - low VulnerabilityStatus: type: string enum: - open - in_progress - snoozed - fixed - ignored - not_affected ScanStatus: type: string enum: - pending - running - completed - failed - cancelled RetestOutcome: type: string enum: - running - still_present - inconclusive - not_reproduced - failed - cancelled description: >- The state of a retest. `running` means the retest scan is pending or running. `still_present` means the retest reproduced the issue. `inconclusive` means the retest completed but could not verify the issue, for example because the target did not respond; the issue keeps its status. If the service was taken down on purpose, close these issues with `POST /vulnerabilities/bulk-update` and `status: fixed`. `not_reproduced` means the retest completed and did not find the issue. `failed` and `cancelled` mirror the retest scan status. ApiV1Scope: type: string enum: - scans:read - scans:write - vulnerabilities:read - vulnerabilities:write - dependencies:read - schedules:read - schedules:write - assets:read - assets:write - organizations:read - organizations:write - members:read - members:write - invitations:read - invitations:write - webhooks:read - webhooks:write - tokens:write - audit:read - pr_reviews:read - pr_reviews:write - connectors:read - connectors:write - knowledge:read - knowledge:write - uploads:write - integrations:read - integrations:write - chat:read - chat:write - scans:message - analytics:read - llm:read - llm:write - test_users:read - test_users:write - discovery:read - discovery:write - license:read - supply_chain:read - supply_chain:write - billing:read - billing:write - containers:read - containers:write - logs:read responses: Unauthorized: description: Missing or invalid API token. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' Forbidden: description: >- Insufficient permissions or missing scope. A missing scope returns the `insufficient_scope` code, the `required_scope` field, and a `hint` with the command or page that grants the scope, so a client can request the correct scope and retry. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' NotFound: description: Resource not found. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' InternalError: description: Internal server error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: BearerAuth: type: http scheme: bearer description: >- API token obtained from the Tokens endpoint or CLI device login. Include as `Authorization: Bearer `. Requests made with a managed CLI session also include `X-Strix-Workspace: ` to pin a process to the workspace it started in; recovery endpoints report the current workspace after a concurrent switch. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.