- You can make the following calls on the session id and user id (if relevant) you find in the page source when you visit your website yourself as a test run. Try this first with all SandBox values as described above.
When a user takes an action you want to protect
When a user takes an action you want to prevent fraudulent devices from taking, such as signing up for a new account, you can make a call to get the device information in exchange for the session id. These calls will show up in 'Session ID API Activity' of your console's developer page and in the 'Session ID' log.
Checking for new information about a device
If you store a device's id, you can make a call to get information about that device at any time. These calls will show up in the 'Device Fingerprint API Activity' section of your console's developer page and in the 'Device Fingerprinting' log.
When a user commits fraud
When a user commits fraud, label the device as bad. These calls will show up in the 'Device Label API Activity' section of your console's developer page and in the 'Device Label' log.
Note: You can both label and un-label a device as 'bad' or 'not_bad' in order to maintain both a blacklist and a whitelist! See here for more details.
When you want to get all the devices for a user