Risk types and codes
What the four-digit codes in the Fraud API’s riskTypes field mean, and how to block on them.
Fraud API v3 returns a riskTypes field next to probability. Each entry is a four-digit integer code for a type of invalid traffic (IVT) in Pixalate’s IVT Taxonomy 2.0. The codes tell you why an IP address, device ID or user agent is flagged, and you can use them in blocking rules.
For the request itself, see the Fraud API guide and the API reference.
How riskTypes behaves
- It lists the risk types associated with all the values you sent (
ip,deviceId,userAgent) during the look-back period, so it can contain more than one code. - It’s
nullwhenprobabilityis0(not flagged) or-1(whitelisted). - It’s
nullwhen a value is flagged but no risk type is available for it. - It’s never an empty array, and each code appears at most once.
Code format
Each code follows the format T C NN:
For example, 2201 is Invalid Proxy Traffic: class 2 (SIVT), category 2 (False Representation), type 01.
Block by class, category or type
Because the code is structured, you can match at any level:
You can use these rules on their own or together with a probability threshold. See Decide when to block.
Categories
Codes
The tables list every type in IVT Taxonomy 2.0. Types marked Upcoming are defined in the taxonomy but aren’t live yet. A lookup returns only the codes associated with the values you sent.
GIVT: Irregular Pattern (11xx)
GIVT: Known Crawlers (12xx)
GIVT: Data Center (13xx)
GIVT: Invalid Placements (14xx)
SIVT: Automated Browsing (21xx)
SIVT: False Representation (22xx)
SIVT: Incentivized Human Invalid Activity (23xx)
SIVT: Misleading User Interface (24xx)
SIVT: Known Dangerous Sources (25xx)
SIVT: Supply Chain (26xx)
Handle new codes
Pixalate may add types to the taxonomy. Write your rules so that an unfamiliar code doesn’t break your integration: match on the class or category prefix where you can, and log codes you don’t recognize.