Get device information
Please refer to API Authentication for API URL and authentication.
This endpoint should only be used for cases where latency is critical and only the device data is required. For non-latency critical cases, please use the customers API endpoint.
There may be some undocumented fields in our API response. Please ignore them as they may be present for backward compatibility or it may be in beta version.
Authorizations
Basic authentication header of the form Basic <encoded-value>
, where <encoded-value>
is the base64-encoded string username:password
.
Body
Identifier for the session passed from the client
Name of the checkpoints to be invoked. Allowed values are device
and login
. Defaults to device
if omitted. Please discuss with Sardine.
device
, login
Referral code
Device details
Response
Device riskiness level and associated signals
Device ID. Also known as HardID or ExactID. This is a cookie that is placed on the customer's browser.
Riskiness of the device session: "very_high", "high", "medium", or "low". This is computed using device checkpoint.
Fingerprint of the device/browser at a global level, also known as SoftID or FuzzyID, based on a hash of different attributes on the device. There can be overlap, hence the related fingerprintConfidenceScore.
confidence of fingerprint being unique from 0 to 100
Reputation of the device across our network (eg if we have seen any fraud report for this device): "very_high_risk", "high_risk", "medium_risk", "low_medium_risk", "low_risk" or "unknown"
Attributes of the device like OS, Model & Browser. Please expand to see field description.
| Name | Description |Values| |--------|---------|-----------| | TrueOS | True OS of device e.g. BlueStacks Android Emulator running on Mac will get TrueOS of Mac instead of Android. |Windows, Linux/Android, Mac/iOS, Unknown| | OSAnomaly| Likelihood of OS anomaly between the TrueOS vs OS sent by the device|high/medium/low | | DeviceAgeHours | Hours since we have first seen the device. | 1| | TrueIP | True IP Address behind IP masking tools |Sample Value: 127.0.0.1| | VPN | The likelihood of the network connection being a VPN| "high", "medium", or "low" | | Proxy | The likelihood of network connection being a Proxy | "high", "medium", or "low" | | Emulator | Is the device an emulator eg Bluestacks - Android, Selenium - Web | true/false | | Rooted | Is the device rooted? (mobile SDK only) | true/false | | RemoteSoftwareLevel | Is the device controlled via Remote Software like TeamViewer, AnyDesk, etc ?| high/medium/low | | IpType | Ip address type |"Commercial", "Organization","Government", "Military", "Education", "Library", "Fixed Line ISP", "Mobile ISP", "Data Center", "Fixed Line ISP / Mobile ISP", "Invalid IP" and "Unknown" | | AccountDeviceId | Account level device ID that is resistant to minor changes; fingerprint at the user account level to help with login anomalies |123| | behaviorBiometricLevel | Riskiness from behavior|high/medium/low|
Session Key
The bot score of the device.
Location data got from IP Address
Location data got from GPS coordinate (available only if your application has user's permission to collect user's location)
Behavior biometric data Signals
Result of rule evaluations for each checkpoint. device
checkpoint is executed by default.