Address
Address get
Request example:
POST <base_path>/v2/address/getBatch HTTP/1.1
Host: api.xxxx.com
Content-Type: application/json
X-Cbc-App-Id: hxgmau9imt86qky9
X-Cbc-Key-Version: admin
X-Cbc-Timestamp: 1792382460
X-Cbc-Nonce: 7c1e9a3b5d7f9b1d3f5a7c9e1b3d5f7a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{"coin":"hc"}
resp, err := client.Post("/v2/address/getBatch", map[string]any{
"coin": "hc",
})
$resp = $client->post('/v2/address/getBatch', [
'coin' => 'hc',
]);
const resp = await client.post('/v2/address/getBatch', {
coin: 'hc',
});
String resp = client.post("/v2/address/getBatch", Map.of("coin", "hc"));
Example of return result:
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
X-Request-ID: 4bf92f3577b34da6a3ce929d0e0e4736
X-Cbc-Timestamp: 1792382461
X-Cbc-Nonce: 3b5d7f9a1c3e5b7d9f1a3c5e7b9d1f3a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{
"status":200,
"msg":"Request succeeded",
"data":[
"HsZWVPmCS92hXJ4mUpTwCs3DX74MK1ihEBn",
"HsCt7eYaJJkn331ZkprcbvGFDrRuqMYcAHx"
],
"date_time":"2020-06-29 14:43:17",
"time_stamp":1593412997
}
Other response examples:
{
"status": 500,
"msg": "Insufficient address",
"data": null,
"date_time": "2020-01-09 15:46:14"
}
{
"status":551,
"msg":"There are 6 allocated unused addresses, please use them up before requesting a new address",
"data":"6",
"date_time":"2020-03-05 10:46:24",
"time_stamp":1583376384
}
- Function: Return the new address to the merchant
- The number of addresses obtained at a time is N (default 200, return only 2 on test env), and merchants can request multiple times according to actual needs.
- For accounts like eos + memo mode, this interface only returns memo, with the interface: /address/coinAccount
- Note: EVM main chains such as eth and bnb_bsc(BNB Smart Chain) share the eth address on the platform. When requesting the address-related api, please use eth as the parameter value of coin (coin=eth). Main chain networks that share the eth address: eth, bnb_bsc, pol, eth_optimism, eth_arbitrum, eth_base, avax_c, eth_zksync, etc.
HTTP Request
POST /v2/address/getBatch
Request Parameters
For the common headers see Signature Regulations; the table below lists only the business parameters in the body.
| Parameter | Required | Type | Description |
|---|---|---|---|
| coin | Yes | string | main chain coin name within 12 characters, the coin name platform shall prevail (if bnb_bsc please use eth). Can query /coin/list to get available coins |
Response Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
| status | Yes | integer | status code |
| msg | No | string | within 100 characters Status description |
| data | No | object | status 200 returns an array of addresses, 500 returns null for insufficient addresses, 551 has allocated unused addresses, returns unused numbers |
| date_time | No | string | Beijing time: 2020-06-29 14:28:14 |
| time_stamp | No | string | response time in seconds: 1593412094 |
The contract coin and the main chain coin share the same address. Please only use the main chain coin name to apply. It is not supported to apply for the address by the contract coin name. Only one main chain coin address can be allocated. Example: user_coin table
| User ID | coin name | Address |
|---|---|---|
| 1688 | eth | 0xa6f8745c56a7c4fcb094678a2fbdcbd9ee9228f7 |
| 1688 | usdt_erc20 | 0xa6f8745c56a7c4fcb094678a2fbdcbd9ee9228f7 |
| 1688 | leek | 0xa6f8745c56a7c4fcb094678a2fbdcbd9ee9228f7 |
- Note: The above addresses belong to the eth main chain address, and can also receive eth contract coins
Address list
Request example:
POST <base_path>/v2/address/list HTTP/1.1
Host: api.xxxx.com
Content-Type: application/json
X-Cbc-App-Id: hxgmau9imt86qky9
X-Cbc-Key-Version: admin
X-Cbc-Timestamp: 1792382460
X-Cbc-Nonce: 7c1e9a3b5d7f9b1d3f5a7c9e1b3d5f7a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{"coin":"hc","address":"HsHGWeEMmx5QLds9UiWfjxarM4RbLAc3xrD","is_used":1,"page":1}
resp, err := client.Post("/v2/address/list", map[string]any{
"coin": "hc",
"address": "HsHGWeEMmx5QLds9UiWfjxarM4RbLAc3xrD",
"is_used": 1,
"page": 1,
})
$resp = $client->post('/v2/address/list', [
'coin' => 'hc',
'address' => 'HsHGWeEMmx5QLds9UiWfjxarM4RbLAc3xrD',
'is_used' => 1,
'page' => 1,
]);
const resp = await client.post('/v2/address/list', {
coin: 'hc',
address: 'HsHGWeEMmx5QLds9UiWfjxarM4RbLAc3xrD',
is_used: 1,
page: 1,
});
String resp = client.post("/v2/address/list", Map.of(
"coin", "hc",
"address", "HsHGWeEMmx5QLds9UiWfjxarM4RbLAc3xrD",
"is_used", 1,
"page", 1));
Example of return result:
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
X-Request-ID: 4bf92f3577b34da6a3ce929d0e0e4736
X-Cbc-Timestamp: 1792382461
X-Cbc-Nonce: 3b5d7f9a1c3e5b7d9f1a3c5e7b9d1f3a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{
"status":200,
"msg":"Processing successful",
"data":{
"page":1,
"max_page":1,
"count":4,
"list":[
{
"address":"HsHGWeEMmx5QLds9UiWfjxarM4RbLAc3xrD",
"user_id":""
},
{
"address":"HsDZKWmgusF7fYbJ1Xw6FJJWx5Bkykdcfq9",
"user_id":""
}
]
},
"date_time":"2020-04-26 17:26:09",
"time_stamp":1587893169
}
- Query address usage status, address ownership.
HTTP Request
POST /v2/address/list
Request Parameters
For the common headers see Signature Regulations; the table below lists only the business parameters in the body.
| Parameter | Required | Type | Description |
|---|---|---|---|
| coin | Yes | string | main chain coin name - see the description of the public information of supported coins (if bnb_bsc please use eth) |
| address | No | string | address |
| page | No | integer | 1<= N <=Max, if it exceeds Max, take Max, if it is less than 1, return 1 |
| is_used | No | integer | 1=used, 2=not used |
Response Parameters
| Parameter | Type | Description |
|---|---|---|
| status | integer | status code |
| msg | string | status description |
| data | object | **See below** "data details". |
| data.page | integer | current page |
| data.max_page | integer | total pages |
| data.count | integer | Number of records on this page |
| data.list | array | record |
| date_time | string | response time |
| time_stamp | integer | timestamp in seconds |
eos-like address + memo mode
Request example:
POST <base_path>/v2/address/coinAccount HTTP/1.1
Host: api.xxxx.com
Content-Type: application/json
X-Cbc-App-Id: hxgmau9imt86qky9
X-Cbc-Key-Version: admin
X-Cbc-Timestamp: 1792382460
X-Cbc-Nonce: 7c1e9a3b5d7f9b1d3f5a7c9e1b3d5f7a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{"coin":"eos"}
resp, err := client.Post("/v2/address/coinAccount", map[string]any{
"coin": "eos",
})
$resp = $client->post('/v2/address/coinAccount', [
'coin' => 'eos',
]);
const resp = await client.post('/v2/address/coinAccount', {
coin: 'eos',
});
String resp = client.post("/v2/address/coinAccount", Map.of("coin", "eos"));
Example of return result:
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
X-Request-ID: 4bf92f3577b34da6a3ce929d0e0e4736
X-Cbc-Timestamp: 1792382461
X-Cbc-Nonce: 3b5d7f9a1c3e5b7d9f1a3c5e7b9d1f3a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{
"status":200,
"msg":"Request succeeded",
"data":"hyperpayeos1",
"date_time":"2020-04-08 18:20:33",
"time_stamp":1586341233
}
Request Parameters
For the common headers see Signature Regulations; the table below lists only the business parameters in the body.
| Parameter | Required | Type | Description |
|---|---|---|---|
| coin | Yes | string | main chain coin name - see the description of the public information of supported coins (if bnb_bsc please use eth) |
Response Parameters
| Parameter | Type | Description |
|---|---|---|
| status | integer | status code |
| msg | string | state description |
| data | object | |
| date_time | string | response time |
| time_stamp | integer | timestamp in seconds |
Address state synchronization
Request example:
POST <base_path>/v2/address/syncStatus HTTP/1.1
Host: api.xxxx.com
Content-Type: application/json
X-Cbc-App-Id: hxgmau9imt86qky9
X-Cbc-Key-Version: admin
X-Cbc-Timestamp: 1792382460
X-Cbc-Nonce: 7c1e9a3b5d7f9b1d3f5a7c9e1b3d5f7a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{"coin":"eth","address":"0xb930c8149bc0bbb0214ae4207164d3b1cb41f395","user_id":"28"}
resp, err := client.Post("/v2/address/syncStatus", map[string]any{
"coin": "eth",
"address": "0xb930c8149bc0bbb0214ae4207164d3b1cb41f395",
"user_id": "28",
})
$resp = $client->post('/v2/address/syncStatus', [
'coin' => 'eth',
'address' => '0xb930c8149bc0bbb0214ae4207164d3b1cb41f395',
'user_id' => '28',
]);
const resp = await client.post('/v2/address/syncStatus', {
coin: 'eth',
address: '0xb930c8149bc0bbb0214ae4207164d3b1cb41f395',
user_id: '28',
});
String resp = client.post("/v2/address/syncStatus", Map.of(
"coin", "eth",
"address", "0xb930c8149bc0bbb0214ae4207164d3b1cb41f395",
"user_id", "28"));
Example of return result:
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
X-Request-ID: 4bf92f3577b34da6a3ce929d0e0e4736
X-Cbc-Timestamp: 1792382461
X-Cbc-Nonce: 3b5d7f9a1c3e5b7d9f1a3c5e7b9d1f3a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{
"status":200,
"msg":"Successful synchronization",
"data":{
"address":"0x0603b5a606e6ae28e729d145f4d5a99bd8769950",
"coin":"eth"
},
"date_time":"2020-01-14 00:33:58"
}
- After the merchant assigns the address to the user, it must notify the platform to update the address usage status through the "Status Synchronization Interface".
HTTP Request
POST /v2/address/syncStatus
Request Parameters
For the common headers see Signature Regulations; the table below lists only the business parameters in the body.
| Parameter | Required | Type | Description |
|---|---|---|---|
| coin | Yes | string | Within 12 characters, the main chain currency of the address (if bnb_bsc, please pass eth) |
| address | Yes | string | address, within 128 characters |
| user_id | Yes | string | User id related to the address, consists of letters, numbers, and underscores. length under 40. |
Response Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
| status | Yes | integer | return status code |
| msg | Yes | string | status code description |
| date_time | Yes | string | interface return time |
| time_stamp | Yes | string | no time zone time unit seconds |
| data | Yes | object | return data |
Note: After the merchant assigns the address to its own user, it must request the interface to return the usage status information, and obtain the correct status code return value of 200 before enabling the user's deposit and withdrawal function.
*1. If it is not synchronized, it will affect the use of the address acquisition interface (when the number of allocated unused addresses exceeds a certain amount, the platform will no longer allocate new addresses to merchants).
*2. If the status synchronization does not receive the correct return result, but reports an error prompt, please manually troubleshoot the error.
Design rules: The same currency or contract currency, the same merchant, and the same user ID can only be assigned one address.
If the above rules are violated, an error will be reported.
Address status batch synchronization
Request example:
POST <base_path>/v2/address/syncBatchStatus HTTP/1.1
Host: api.xxxx.com
Content-Type: application/json
X-Cbc-App-Id: hxgmau9imt86qky9
X-Cbc-Key-Version: admin
X-Cbc-Timestamp: 1792382460
X-Cbc-Nonce: 7c1e9a3b5d7f9b1d3f5a7c9e1b3d5f7a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{"address_list":[{"address":"0x038B8E7406dED2Be112B6c7E4681Df5316957cad","coin":"eth","user_id":"123sa"},{"address":"0xf854AC319A546ae11e367ef80a203AaC923ca6A3","coin":"eth","user_id":"123sb"}]}
resp, err := client.Post("/v2/address/syncBatchStatus", map[string]any{
"address_list": []map[string]any{
{"address": "0x038B8E7406dED2Be112B6c7E4681Df5316957cad", "coin": "eth", "user_id": "123sa"},
{"address": "0xf854AC319A546ae11e367ef80a203AaC923ca6A3", "coin": "eth", "user_id": "123sb"},
},
})
$resp = $client->post('/v2/address/syncBatchStatus', [
'address_list' => [
['address' => '0x038B8E7406dED2Be112B6c7E4681Df5316957cad', 'coin' => 'eth', 'user_id' => '123sa'],
['address' => '0xf854AC319A546ae11e367ef80a203AaC923ca6A3', 'coin' => 'eth', 'user_id' => '123sb'],
],
]);
const resp = await client.post('/v2/address/syncBatchStatus', {
address_list: [
{ address: '0x038B8E7406dED2Be112B6c7E4681Df5316957cad', coin: 'eth', user_id: '123sa' },
{ address: '0xf854AC319A546ae11e367ef80a203AaC923ca6A3', coin: 'eth', user_id: '123sb' },
],
});
String resp = client.post("/v2/address/syncBatchStatus", Map.of(
"address_list", List.of(
Map.of("address", "0x038B8E7406dED2Be112B6c7E4681Df5316957cad", "coin", "eth", "user_id", "123sa"),
Map.of("address", "0xf854AC319A546ae11e367ef80a203AaC923ca6A3", "coin", "eth", "user_id", "123sb"))));
Example of return result:
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
X-Request-ID: 4bf92f3577b34da6a3ce929d0e0e4736
X-Cbc-Timestamp: 1792382461
X-Cbc-Nonce: 3b5d7f9a1c3e5b7d9f1a3c5e7b9d1f3a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{
"status":200,
"msg":"Request succeeded",
"data":{
"success_data":[
{
"address":"0x038B8E7406dED2Be112B6c7E4681Df5316957cad",
"user_id":"123sa",
"coin":"eth"
}
],
"fail_data":[
{
"address":"0xf854AC319A546ae11e367ef80a203AaC923ca6A3",
"user_id":"123sb",
"coin":"eth",
"msg":"The address has been assigned to other users and cannot be assigned repeatedly",
"status":524,
"owner_user_id":"345ad"
}
]
},
"date_time":"2021-03-22 10:55:58",
"time_stamp":1616381758
}
- After the merchant assigns the address to the user, it must notify the platform to update the address usage status through the "status synchronization interface", which supports batch synchronization (recommended at most 100 at a time).
HTTP Request
POST /v2/address/syncBatchStatus
Request Parameters
For the common headers see Signature Regulations; the table below lists only the business parameters in the body.
| Parameter | Required | Type | Length | Description |
|---|---|---|---|---|
| address_list | Yes | array | ||
| address_list.address | Yes | string | within 128 characters | address |
| address_list.coin | Yes | string | Within 12 characters | The currency of the main chain to which the address belongs (if bnb_bsc, please pass eth) |
| address_list.user_id | Yes | string | string within 40 | User id related to the address, consists of letters, numbers, and underscores. |
Response Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
| status | Yes | integer | return status code |
| msg | Yes | string | status code description |
| date_time | Yes | string | interface returns time |
| time_stamp | Yes | string | no time zone time unit seconds |
| success_data | Yes | object | success assignment information |
| success_data.address | Yes | string | address |
| success_data.coin | Yes | string | coin name |
| success_data.user_id | Yes | string | business user id |
| fail_data | Yes | object | failed assignment information |
| fail_data.address | Yes | string | address |
| fail_data.coin | Yes | string | coin name |
| fail_data.user_id | Yes | string | merchant user id |
| fail_data.status | Yes | string | failure code |
| fail_data.msg | Yes | string | description of failure reason |
| fail_data.old_address | Yes | string | address information that the user id has been bound to |
| fail_data.owner_user_id | Yes | string | user information bound to the current address |
Note: After the merchant assigns the address to its own user, it must request the interface to return the usage status information, and obtain the correct status code return value of 200 before enabling the user's deposit and withdrawal function.
1. If it is not synchronized, it will affect the use of the address acquisition interface (when the number of allocated unused addresses exceeds a certain amount, the platform will no longer allocate new addresses to merchants).
2. If the status synchronization does not receive the correct return result, but reports an error prompt, please manually troubleshoot the error.
Design rules: The same currency or contract currency, the same merchant, and the same user ID can only be assigned one address.
If the above rules are violated, an error will be reported.
Address verification
Request example:
POST <base_path>/v2/address/verifyAddress HTTP/1.1
Host: api.xxxx.com
Content-Type: application/json
X-Cbc-App-Id: hxgmau9imt86qky9
X-Cbc-Key-Version: admin
X-Cbc-Timestamp: 1792382460
X-Cbc-Nonce: 7c1e9a3b5d7f9b1d3f5a7c9e1b3d5f7a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{"coin":"trx","address":"TUEgUZh24tA48EXiAQjA6Qf6rSS7bJKQ6g"}
resp, err := client.Post("/v2/address/verifyAddress", map[string]any{
"coin": "trx",
"address": "TUEgUZh24tA48EXiAQjA6Qf6rSS7bJKQ6g",
})
$resp = $client->post('/v2/address/verifyAddress', [
'coin' => 'trx',
'address' => 'TUEgUZh24tA48EXiAQjA6Qf6rSS7bJKQ6g',
]);
const resp = await client.post('/v2/address/verifyAddress', {
coin: 'trx',
address: 'TUEgUZh24tA48EXiAQjA6Qf6rSS7bJKQ6g',
});
String resp = client.post("/v2/address/verifyAddress", Map.of(
"coin", "trx",
"address", "TUEgUZh24tA48EXiAQjA6Qf6rSS7bJKQ6g"));
Example of return result:
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
X-Request-ID: 4bf92f3577b34da6a3ce929d0e0e4736
X-Cbc-Timestamp: 1792382461
X-Cbc-Nonce: 3b5d7f9a1c3e5b7d9f1a3c5e7b9d1f3a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{
"status":200,
"msg":"Verification succeeded",
"data":null,
"date_time":"2020-10-20 15:32:16",
"time_stamp":1603179136
}
- Address validity verification, currently only supports eth, trx, btc main chain address verification, and will continue to expand other main chain address verification in the future
HTTP Request
POST /v2/address/verifyAddress
Request Parameters
For the common headers see Signature Regulations; the table below lists only the business parameters in the body.
| Parameter | Required | Type | Description |
|---|---|---|---|
| coin | Yes | string | Main chain coin name within 12 characters, the coin name provided by the platform shall prevail |
| address | Yes | string | address |
Response Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
| status | Yes | integer | Return value: 200 Verification successful; 543 Verification failed; 565 Currency not supported |
| msg | No | string | within 100 characters, state description |
| data | Yes | object | — |
| date_time | No | string | Beijing time: 2020-06-29 14:28:14 |
| time_stamp | No | string | response time in seconds: 1593412094 |
- Note: The above addresses belong to the eth main chain address, and can also receive eth contract coin
Address AML verification
Request example:
POST <base_path>/v2/address/verifyAml HTTP/1.1
Host: api.xxxx.com
Content-Type: application/json
X-Cbc-App-Id: hxgmau9imt86qky9
X-Cbc-Key-Version: admin
X-Cbc-Timestamp: 1792382460
X-Cbc-Nonce: 7c1e9a3b5d7f9b1d3f5a7c9e1b3d5f7a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{"chain":"trx","address":"TUEgUZh24tA48EXiAQjA6Qf6rSS7bJKQ6g","skip_api_source":"OK_LINK"}
resp, err := client.Post("/v2/address/verifyAml", map[string]any{
"chain": "trx",
"address": "TUEgUZh24tA48EXiAQjA6Qf6rSS7bJKQ6g",
"skip_api_source": "OK_LINK",
})
$resp = $client->post('/v2/address/verifyAml', [
'chain' => 'trx',
'address' => 'TUEgUZh24tA48EXiAQjA6Qf6rSS7bJKQ6g',
'skip_api_source' => 'OK_LINK',
]);
const resp = await client.post('/v2/address/verifyAml', {
chain: 'trx',
address: 'TUEgUZh24tA48EXiAQjA6Qf6rSS7bJKQ6g',
skip_api_source: 'OK_LINK',
});
String resp = client.post("/v2/address/verifyAml", Map.of(
"chain", "trx",
"address", "TUEgUZh24tA48EXiAQjA6Qf6rSS7bJKQ6g",
"skip_api_source", "OK_LINK"));
Example of return result:
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
X-Request-ID: 4bf92f3577b34da6a3ce929d0e0e4736
X-Cbc-Timestamp: 1792382461
X-Cbc-Nonce: 3b5d7f9a1c3e5b7d9f1a3c5e7b9d1f3a
X-Cbc-Sign-Alg: RSA-SHA256
X-Cbc-Signature: <base64>
{
"data": {
"address": "0x8e609ac80f4324e499a6efd24f221a2caa868224",
"chain": "eth",
"detail": "{\"Suspicious transaction\":[\"High proportion of large-value transactions\",\"High-frequency trading behavior\",\"Highly concentrated transactions\"],\"Blacklisted address affiliate\":[\"Hacker affiliate\"]}",
"level": "MEDIUM",
"risk_code": 5103,
"risk_score": "62",
"source": "OK_LINK",
"tag": "Medium risk: blacklisted address affiliate; suspicious transaction"
},
"date_time": "2023-11-22 18:19:54",
"msg": "SUCCESS",
"status": 200,
"time_stamp": 1700648394
}
- Address AML verification. Current support btc,eos,etc,eth,trx,usdt,xrp. If you need support this feature, please contact customer service.
HTTP Request
POST /v2/address/verifyAml
Request Parameters
For the common headers see Signature Regulations; the table below lists only the business parameters in the body.
| Parameter | Required | Type | Description |
|---|---|---|---|
| chain | Yes | string | Main chain coin name within 12 characters, the coin name provided by the platform shall prevail. May be omitted when coin is set; if both are set they must match |
| address | Yes | string | address |
| skip_api_source | No | string | Specify the aml source that skips remote api query, you can fill in the source OK_LINK or BEOSIN, separated by multiple commas. The premise is that the corresponding source has been activated through customer service. |
| source | No | string | Match only the given AML source; currently only BEOSIN is supported, other values return 522 |
| coin | No | string | Coin name, used by Beosin only. When set, the main chain of this coin is used |
| contract_address | No | string | Contract address, used by Beosin only. When sent together with coin it must match the contract address of that coin |
Response Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
| status | Yes | integer | Return value: 200 success |
| msg | No | string | within 100 characters, state description |
| data | Yes | object | — |
| data.chain | Yes | string | main coin name of chain |
| data.address | Yes | string | address |
| data.risk_code | Yes | integer | risk code. default value 0, means no risk. Non Zero means there is risk, and more code will be added later. |
| data.source | Yes | string | AML data source, OK_LINK,SLOW_MIST,BEOSIN |
| data.tag | No | string | risk tags. OK_LINK may return this text in Chinese |
| data.detail | No | string | risk description. OK_LINK may return this text in Chinese |
| data.risk_score | No | string | OK_LINK risk score, value 100 means no risk.The lower the score, the higher the risk. |
| data.level | No | string | OK_LINK risk level, SEVERE,HIGH,MEDIUM,LOW,NONE |
| date_time | No | string | Beijing time: 2020-06-29 14:28:14 |
| time_stamp | No | string | response time in seconds: 1593412094 |
risk_code description
| risk_code | description |
|---|---|
| 0 | no risk |
| 5001 | Extortion involving malicious mining activities |
| 5002 | money theft attacks |
| 5003 | phishing attacks |
| 5004 | phishing attacks involving cybercrime |
| 5101 | SEVERE risk level(source OK_LINK) |
| 5102 | HIGH risk level(source OK_LINK) |
| 5103 | MEDIUM risk level(source OK_LINK) |
| 5104 | LOW risk level(source OK_LINK) |
| 5201 | Severe risk level(source BEOSIN) |
| 5202 | High risk level(source BEOSIN) |
| 5203 | Medium risk level(source BEOSIN) |
| 5204 | Low risk level(source BEOSIN) |
| xxxx | may more codes ... |