Verify a test user's login
Starts a short agent run (usually a minute or two) that drives the target’s real login form with the saved credentials and reports a structured outcome, so a broken login surfaces before a scan. Returns 202 with a pending verification, or 200 with an in-flight / recent one that is reused. The login URL must use HTTP(S). Network test users can use private addresses because verification runs on the selected network.
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
Query Parameters
Body
Custom HTTP headers the scan will send, for example a bot-protection bypass header. The verification sends them on requests to the login URL's origin, so the check reaches the login page the same way the scan will. Values are stored encrypted and never returned. Rows with a blank name or value are ignored.
10Response
An in-flight or recent verification was reused.
Outcome of a pre-scan login verification run for a saved test user.