Updating Crypto Screening from Single to Multi-Asset

We are proud to announce a significant update to our Crypto Screening tool - GlobalPass now supports Multi-Asset Crypto Screening, which expands our crypto analytics coverage to 38 blockchains instead of the previous 3, and makes all screening requests unified, no matter what blockchain or asset is screened.

The new holistic multi-asset screening will fully replace the current single-asset screening, offering more comprehensive and detailed analysis. This article explains how to update your existing single-asset integration to gain access to the new features.

Transaction Screening Request

When initiating a Multi-Asset Transaction Scan instead of Single-Asset, you should:

make a POST request to the V3 endpoint instead of V2
make a unified request, no matter what asset you are screening:
1. do not include blockchain, ticker, outputIndices and logIndex values anymore
2. all remaining values are now required, including outputAddress, which was previously required only for Bitcoin and Tron transactions

Single-Asset Transaction Request (V2)

/api/v2/crypto/transactions

Multi-Asset Transaction Request (V3)

/api/v3/crypto/transactions

{
"blockchain": "string",
"ticker": "string",
"hash": "string",
"direction": "string",
"outputAddress": "string",
"outputIndices": [
0
],
"logIndex": 0,
"externalId": "string"
}

{
"hash": "string",
"direction": "string",
"outputAddress": "string",
"externalId": "string"
}

Wallet Screeing Request

When initiating a Multi-Asset Wallet Scan instead of Single-Asset, you should:

make a POST request to the V3 endpoint instead of V2
do not include blockchain and ticker values anymore
both remaining values (address and externalID) remain required

Single-Asset Wallet Request (V2)

/api/v2/crypto/wallets

Multi-Asset Wallet Request (V3)

/api/v3/crypto/wallets

{
"blockchain": "string",
"ticker": "string",
"address": "string",
"externalId": "string"
}

{
"address": "string",
"externalId": "string"
}

Transaction & Wallet Screening Response

The successful scan responses (both transaction and wallet) do not contain any changes from Single-Asset successful scan response.

The 400 Bad Request responses now contain specific error name together with error message, instead of previous generalErrors error name.

Single-Asset Transaction/Wallet (V2)

400 Bad Request Response example

Multi-Asset Transaction/Wallet (V3)

400 Bad Request Response example

{
"errors": {
"generalErrors": [
"The submitted address with hash example123 has not yet been processed into the screening tool or does not exist on the blockchain."
]
}
}

{
"errors": {
"notInBlockchain": [
"The submitted address with hash example123 has not yet been processed into the screening tool or does not exist on the blockchain."
]
}
}

There are no other changes in transaction or wallet scan responses.

Requesting Screening Results

To make a request to retrieve results of any given crypto transaction or wallet screening, make a GET request to the new V3 endpoints instead of the previous V2. The V3 endpoints will also work to request results of older single-asset screenings.

Transactions:

Instead of /api/v2/crypto/transactions/{screeningToken}
Call /api/v3/crypto/transactions/{screeningToken}

Wallets:

Instead of /api/v2/crypto/wallets/{screeningToken}
Call /api/v3/crypto/wallets/{screeningToken}