Get a detailed analysis of an individual identification event, including Smart Signals.
Use event_id as the URL path parameter. This API method is scoped to a request, i.e. all returned information is by event_id.
Add your Secret API Key to the Authorization header using the standard Bearer format: Authorization: Bearer <secret_api_key>
The unique identifier of each identification request (requestId can be used in its place).
OK.
Contains results from Fingerprint Identification and all active Smart Signals.
Unique identifier of the user's request. The first portion of the event_id is a unix epoch milliseconds timestamp For example: 1758130560902.8tRtrH
Timestamp of the event with millisecond precision in Unix time.
A customer-provided id that was sent with the request.
Environment Id of the event. For example: ae_47abaca3db2c7c43
Field is true if you have previously set the suspect flag for this event using the Server API Update event endpoint.
Contains information about the SDK used to perform the request.
true if we determined that this payload was replayed, false otherwise.
A supplementary browser identifier that prioritizes coverage over precision. The High Recall ID algorithm matches more generously, i.e., this identifier will remain the same even when there are subtle differences between two requests. This algorithm does not create as many new visitor IDs as the standard algorithms do, but there could be an increase in false-positive identification.
A customer-provided value or an object that was sent with the identification request or updated later.
Page URL from which the request was sent. For example https://example.com/
Bundle Id of the iOS application integrated with the Fingerprint SDK for the event. For example: com.foo.app
Package name of the Android application integrated with the Fingerprint SDK for the event. For example: com.foo.app
IP address of the requesting browser or bot.
User Agent of the client, for example: Mozilla/5.0 (Windows NT 6.1; Win64; x64) ....
Client Referrer field corresponds to the document.referrer field gathered during an identification request. The value is an empty string if the user navigated to the page directly (not through a link, but, for example, by using a bookmark) For example: https://example.com/blog/my-article
Proximity ID represents a fixed geographical zone in a discrete global grid within which the device is observed.
Bot detection result:
not_detected - the visitor is not a botgood - good bot detected, such as Google bot, Baidu Spider, AlexaBot and so onbad - bad bot detected, such as Selenium, Puppeteer, Playwright, headless browsers, and so onnot_detected, good, bad Additional classification of the bot type if detected.
Android specific cloned application detection. There are 2 values: * true - Presence of app cloners work detected (e.g. fully cloned application found or launch of it inside of a not main working profile detected). * false - No signs of cloned application detected or the client is not Android.
true if the browser is Chrome with DevTools open or Firefox with Developer Tools open, false otherwise.
Android specific emulator detection. There are 2 values:
true - Emulated environment detected (e.g. launch inside of AVD).false - No signs of emulated environment detected or the client is not Android.The time of the most recent factory reset that happened on the mobile device is expressed as Unix epoch time. When a factory reset cannot be detected on the mobile device or when the request is initiated from a browser, this field will correspond to the epoch time (i.e 1 Jan 1970 UTC) as a value of 0. See Factory Reset Detection to learn more about this Smart Signal.
Details about the request IP address. Has separate fields for v4 and v6 IP address versions.
IP address was used by a public proxy provider or belonged to a known recent residential proxy
Confidence level of the proxy detection. If a proxy is not detected, confidence is "high". If it's detected, can be "low", "medium", or "high".
low, medium, high Proxy detection details (present if proxy is true)
true if we detected incognito mode used in the browser, false otherwise.
iOS specific jailbreak detection. There are 2 values:
true - Jailbreak detected.false - No signs of jailbreak or the client is not iOS.Flag indicating whether the request came from a mobile device with location spoofing enabled.
true - When requests made from your users' mobile devices to Fingerprint servers have been intercepted and potentially modified.false - Otherwise or when the request originated from a browser.
See MitM Attack Detection to learn more about this Smart Signal.true if the request is from a privacy aware browser (e.g. Tor) or from a browser in which fingerprinting is blocked. Otherwise false.
Android specific root management apps detection. There are 2 values:
true - Root Management Apps detected (e.g. Magisk).false - No Root Management Apps detected or the client isn't Android.Suspect Score is an easy way to integrate Smart Signals into your fraud protection work flow. It is a weighted representation of all Smart Signals present in the payload that helps identify suspicious activity. The value range is [0; S] where S is sum of all Smart Signals weights. See more details here: https://dev.fingerprint.com/docs/suspect-score
Flag indicating browser tampering was detected. This happens when either:
tampering_details.anomaly_score).tampering_details.anti_detect_browser).Sums key data points for a specific visitor_id, ip_address and linked_id at three distinct time
intervals: 5 minutes, 1 hour, and 24 hours as follows:
The 24h interval of distinct_ip, distinct_linked_id, distinct_country,
distinct_ip_by_linked_id and distinct_visitor_id_by_linked_id will be omitted
if the number of events for the visitor Id in the last 24
hours (events.['24h']) is higher than 20.000.
All will not necessarily be returned in a response, some may be omitted if the associated event does not have the required data, such as a linked_id.
true if the request came from a browser running inside a virtual machine (e.g. VMWare), false otherwise.
VPN or other anonymizing service has been used when sending the request.
A confidence rating for the VPN detection result — "low", "medium", or "high". Depends on the combination of results returned from all VPN detection methods.
low, medium, high Local timezone which is used in timezone_mismatch method.
Country of the request (only for Android SDK version >= 2.4.0, ISO 3166 format or unknown).
Flag indicating if the request came from a high-activity visitor.