Get scan details
Returns full scan details including associated vulnerabilities. A pentest’s list omits dependency CVE findings. A supply-chain scan’s findings are all dependency CVEs. The response embeds them only when the token also holds the dependencies:read scope. Without that scope, the list is empty.
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.
Response
Scan details with vulnerabilities.
pending, running, completed, failed, cancelled Short, secret-free explanation of the login outcome.
Category of the login failure (e.g. invalid_credentials, mfa_required_not_configured).
Whether the agent could log in with the provisioned test credentials, when any were configured: succeeded | failed.
Time when the orchestrator checked the selected cloud connections.
Attachment outcome for each cloud connection selected for the scan.
True for a retest scan. A retest scan verifies one or more existing issues and does not appear in the scan list.
Public provider-resource metadata selected specifically for this scan.
Self-hosted only: per-scan LLM cost limit (USD), if one was set.
Self-hosted only: cost-limit policy the scan runs with, if a limit was set.
stop, pause, null Retest scans only: the scan that found the source issue.
Retest scans only: the title of the parent scan.
The commit each repository was tested at, keyed by the repository URL from repositories. The value is the full commit SHA that the scan checked out. Null for a scan with no repository target and for a scan that ran before Strix recorded commits.
Retest scans that a Retest issue request started: the current state of that issue. Null for a retest that a rerun started, even when retest_target_count is 1.
Retest scans that a rerun started: the scan whose open issues the retest verifies.
Retest scans that a Retest issue request started: the issue that the retest verifies. Null for a retest that a rerun started, even when retest_target_count is 1.
Retest scans only: the number of issues that the retest verifies. 0 for other scans.
Scan tier the run used. A null value means the scan was launched without a tier.
lite, standard, ultra, null whitebox, blackbox Why the engine ended the scan before its agents finished: the cost limit was reached, the model provider rate-limited the scan, or a sub-agent never finished. Null when the agents finished on their own. A retest scan that stopped early does not mark any issue fixed; its issues without a finding are inconclusive.
budget_exceeded, rate_limited, agents_incomplete, null Secret-free explanation of status_detail_code. Self-hosted installs return the exact infrastructure message, for example the Kubernetes scheduler message. The hosted product returns generic wording. For budget_near_limit every install returns the cost figures, for example The run used $96.13 of its $100.00 cost limit (96%)….
Reason code behind the current status. Set when the launch path or the infrastructure set the status, or when a completed scan ended early near its cost limit (budget_near_limit). null for an ordinary engine-owned status.
sandbox_pending, config_missing, llm_not_configured, secrets_missing, connector_unavailable, credentials_unreadable, image_pull_failed, pod_unschedulable, pod_rejected, container_config_failed, volume_failed, sandbox_ended, sandbox_timeout, docker_unavailable, sandbox_create_failed, launch_failed, retest_already_running, watchdog_timeout, launch_no_telemetry, relaunch_failed, relaunches_exhausted, engine_failed, budget_near_limit