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 domain must be ownership-verified. The login URL may live on another host (SSO tenant, IdP, separate auth site) as long as it is a public http(s) endpoint.
Authorizations
API token obtained from the Tokens endpoint. Include as Authorization: Bearer <token>.
Query Parameters
Set to 1 to re-verify even when a recent result exists (use after changing the credentials).
1 Response
An in-flight or recent verification was reused.
Outcome of a pre-scan login verification run for a saved test user.
pending, running, succeeded, failed Category of the failure when status is failed.
invalid_credentials, login_page_not_found, mfa_required_not_configured, mfa_code_unavailable, account_locked, target_unreachable, bot_protection, launch_failed, other, null Human-readable explanation of the outcome. Never contains credentials or email contents.