API & payload
Verify a session and get back a stable Arkose ID, a confidence score, spoofing and network signals, and device details. Here's exactly what the response looks like.
Where it fits
Response shape matches the Arkose Verify API device_id object. Values are illustrative. See full field reference →
Reading the response
arkose_idThe persistent device identifier. Stays stable across sessions even when cookies are cleared, so you can recognize returning devices and link accounts.
confidence_scoreHow certain the match is, 0–100. Set your own threshold to trade off precision against recall.
device_first_seen / device_last_seenDevice age and recency. A brand-new device acting like a veteran is a classic fraud signal.
device_spoofing_detectedFlags devices tampering with their fingerprint, the tell behind payment fraud and fake-account rings.
stateless_device_id / stateful_device_idStateless matching works same-day with your API key; stronger stateful matching switches on once your vanity URL is provisioned.
is_vpn / is_proxy / is_torNetwork-evasion signals from IP intelligence, surfaced alongside the device signal.
device_id.risk_score / risk_bandA 0–100 risk score and Low / Medium / High band scoped to the device itself — not just the session. Map it directly to allow, monitor, or block decisions.
device_id.risk_insightsThe exact signals we spotted on this device — Headless_Browser_Confirmed, Virtual_GPU_Confirmed, Hardware_Signals_Suppressed, Timezone_Mismatch_Detected, and more. Tells you precisely why a device is flagged, not just that it is.
Start a Trial, drop in the tag, and see real device responses from your own traffic within days.
Start a TrialNeed enterprise-scale device intelligence, custom volumes, or the full Arkose Titan platform?
Visit Arkose Labs →