OEM partners can queue scans and retrieve status using the returned scan_id. Both routes require Enterprise authentication and the OEM module.
Allow only assets the tenant owns or is explicitly authorized to test. Enforce scope outside the request body.

Queue a scan

Successful response
A single public IP can be submitted with type: "ip_range"; the service converts it to /32. Private IP ranges are rejected. A non-deduplicated queued request consumes one OEM credit.

Check status

Status response
Status records can include queued, processing states, scan_completed, or failure states. Treat any returned state other than a terminal completion or failure as non-terminal rather than hard-coding only one in-progress value.

Polling pattern

Limits and errors

Use stable query_tags, retain scan_id, set a polling timeout, and reconcile requests through OEM account audit logs. For a resumable worker with an atomic state file, follow Orchestrate an OEM Scan Lifecycle. For a deployment decision that also verifies indexed-data freshness, use Post-Deployment Exposure Verification.