Uploads end-user's device data that has been collected to improve verification results and fight fraud
- This endpoint is used to send detailed technical data about the end-user's device, network environment, and browser characteristics to enhance fraud detection and risk assessment capabilities
- The data is collected by third-party fingerprinting services and submitted during or after the verification flow
When to use this endpoint
- Use this endpoint when you need to submit device intelligence data from third-party fingerprinting providers
Common use cases include:
- Enhancing fraud detection by submitting comprehensive device fingerprints
- Providing network telemetry for risk scoring and geolocation verification
- Submitting browser characteristics and environment data for device intelligence
- Integrating with third-party fraud prevention services that collect device data
Request body content
In this request, only the following fields are mandatory:
providerName:stringName of the fingerprinting service provider, max 255 charactersnetwork.ip:stringEither IPv4 or IPv6 data needs be presentdevice.fingerprint:stringDevice fingerprint, max 255 characters
The rest of the parameters listed below are optional If there is no data to provide, the parameter should not be included in the payload
Response data
The response confirms successful data submission and returns:
- Request status confirmation
sessionIdthat received the collected dataattemptIdassociated with this data submission (see the List attempts endpoint for more info about attempts)
This data becomes part of the verification session's fraud detection signals and risk assessment
Implementation notes
- The session must be in
createdorstartedstatus - Device
fingerprintis the only required field in thedeviceobject - At least one IP address (IPv4 or IPv6) must be provided in
network.ip - The
personobject is optional and used only if additional contact data was collected - This endpoint requires session-level HMAC signature authentication
- Data submitted through this endpoint enhances fraud detection but is not required for basic verification
- Always ensure that you use the correct API URL to send requests See the API URL section for more info.
- The order of parameters in the real API response can differ from the order you see in this documentation. This is expected and part of the Backwards compatible changes requirements.
Your integration's API key (occasionally referred to as the "Token", "API public key" or "Publishable key"). Required for all API requests.
You can find your API key in the Veriff Customer Portal > Settings > API keys.
Request body signed with the shared secret key. Required to authenticate the request sender.
Request content type. Must be application/json.
Verification session ID.
Minimum required fields to submit device fingerprinting data. Only includes the three mandatory parameters.
{
"providerName": "SampleFingerprint",
"network": {
"ip": {
"addressV4": "192.168.1.100"
}
},
"device": {
"fingerprint": "123456asdfg7890hijkl123456asdfg7890hijkl123456asdfg7890hijkl"
}
}Complete device fingerprinting data including all optional fields such as person data, network details, browser characteristics, and device specifications.
{
"providerName": "SampleFingerprint",
"person": {
"email": "firstname.lastname@domain.com",
"phoneNumber": "+11 222 333 44"
},
"network": {
"mobileCarrier": "RandomTeleCom Inc",
"ssid": "MyWiFiNetwork",
"hostname": "examplehostname.amazonaws.com",
"location": {},
"ip": {
"addressV4": "192.168.1.100",
"addressV6": "2001:DB8:0000:XXXX:XXX:17FF:FEB6:XXXX/64"
},
"asn": {
"number": "AS12345",
"organisation": "AWS"
}
},
"device": {
"fingerprint": "123456asdfg7890hijkl123456asdfg7890hijkl123456asdfg7890hijkl",
"androidId": "ab1357cd-a1b2-c3d4-f5g6",
"model": "Samsung Galaxy S23 Ultra",
"vendor": "Samsung",
"type": "mobile",
"browser": {
"languages": [
"en-gb"
],
"userAgent": "Mozilla/5.0 (Linux; Android 13) AppleWebKit/537.36",
"timezoneOffsetMinutes": -240,
"isIncognito": false
},
"audio": {
"devices": [
{
"name": "Built-in Speaker"
}
]
},
"screen": {
"heightPixels": 3088,
"widthPixels": 1440,
"dpi": 500
},
"battery": {
"level": 0.43,
"charging": true
},
"os": {
"family": "Android",
"name": "Android",
"platform": "ARM",
"version": "13"
}
}
}Name of the company providing the fingerprinting service, max 255 characters.
Data about the person being verified.
Person's email address entered during the validation.
Person's phone number.
Can include numbers, whitespaces and the "+" sign in front.
Data about the network used.
Name of the service provider.
Service Set Identifier (SSID) value.
Service host name.
Additional data about the location.
IP info. At least one is mandatory (IPv4 or IPv6).
IPv4 info. Optional if IPv6 info is included.
IPv6 info. Optional if IPv4 info is included.
Autonomous System Number (ASN) info.
Autonomous System Number (ASN).
Name of the organization owning the ASN.
Data related to the device used for verification.
Device fingerprint, max 255 characters.
The Android unique device ID is a combination of 8 digits and letters, followed by a dash and three sets of 4 digits and letters, all letters are lowercase.
The Identifier for Vendors (IDFV) code.
Device model.
Device supplier.
Device type.
Data related to the browser used for verification.
IETF language tag, for example "es-419", "en-gb", "pl".
Browser user agent, max 255 characters.
An integer for the time offset from the UTC, in range from -1440 to +1440 minutes.
Data about whether the incognito mode is on.
Data related to the audio of the device used for verification.
Array of data strings about the audio of the device used for
verification, in format of name : string.
Data related to the screen of the device used for verification.
An integer in range of 1-100000.
An integer in range of 1-100000
An integer in range of 1-100000.
Data related to the battery of the device used for verification.
A float in range of 0.0-1.0.
Data about whether the device is charging.
Data related to the operating system (OS) of the device used for verification.
OS family.
OS name.
OS platform type, for example "x64", "ARM", "OS/390".
OS version.
Collected data posted successfully
Successful data submission
Confirmation that device fingerprinting data was successfully received and associated with the verification session and attempt.
{
"status": "success",
"sessionId": "f04bdb47-d3be-4b28-b028-a652feb060b5",
"attemptId": "f5c68aea-7f4d-478d-80ab-ca9356074f69"
}API request status
UUID v4 which identifies the verification session
UUID v4 which identifies the attempt
Bad request
Missing required field
{
"status": "fail",
"code": "1101",
"message": "Validation failed"
}Invalid data format
{
"status": "fail",
"code": "1101",
"message": "Validation failed"
}Unauthorized
Missing API key
{
"status": "fail",
"code": "1101",
"message": "Mandatory X-AUTH-CLIENT header containing the API key is missing from the request."
}Invalid HMAC signature
{
"status": "fail",
"code": "1101",
"message": "X-HMAC-SIGNATURE validation failed"
}Session not found
Session does not exist
{
"status": "fail",
"code": "1101",
"message": "Resource not found"
}Internal server error
Server processing error
{
"status": "fail",
"code": "1101",
"message": "Something went wrong"
}Changelog
Date | Description |
|---|---|
Mar 9, 2026 | Documentation updated: parent categories rearranged, intro section expanded, request and response examples added |
Oct 2, 2025 |
|
Aug 6, 2025 | Response headers added |
Mar 12, 2025 | Documentation published |