Home Admin guide Platform API Methods for antifraud monitoring

Methods for antifraud monitoring

On this page:

GET[host]/back-api/antifraud/trades/{period}

Get user trades

GET[host]/back-api/antifraud/arbitrages{period}

Get the arbitrage polygon data

Get user trades

Use this method to inspect recent trades made by exchange users.

Request

Header parameters:

  • Authorization: Bearer <access_token>

Path parameters:

period required

The time period for which the trading data must be collected:

  • minute — the last minute

  • minute3 — the last 3 minutes

  • minute5— the last 5 minutes

  • day — the last 24 hours (specify this setting only when obtaining logs for a single user)

user

The username or email (to return entries matching this string).

cursor

The page number, in the range indicated in a previous paging response.

GET[host]/back-api/antifraud/trades/{period}

GET /back-api/antifraud/trades/minute HTTP/1.1
Host: host.name
Authorization: Bearer akvmn34egjidg0jifgjdg0djg34g

Response

userId string

The user identifier, in the GUID string format.

tradesCount number

The total number of trades that have occurred during the specified time period.

RESPONSE EXAMPLE 
[
  {
    "userId": "a9fa79b8-386b-4985-1234-b0c2c5bd2e0e",
    "tradesCount": 3
  }
]

Get the arbitrage polygon data

Use this method to identify possible arbitrage polygons within the context of recent trading activity on the exchange.

Request

Header parameters:

  • Authorization: Bearer <access_token>

Path parameters:

period required

The time period for which the trading data must be collected:

  • minute — the last minute

  • minute3 — the last 3 minutes

  • minute5— the last 5 minutes

  • day — the last 24 hours (specify this setting only when obtaining logs for a single user)

user

The username or email (to return entries matching this string).

cursor

The page number, in the range indicated in a previous paging response.

GET[host]/back-api/antifraud/arbitrages{period}

GET /back-api/antifraud/arbitrages/minute HTTP/1.1
Host: host.name
Authorization: Bearer akvmn34egjidg0jifgjdg0djg34g

Response

email string

The user identifier, in the GUID string format.

arbitrage object

The following information is provided about each located arbitrage polygon (with translating it into a succession of user transactions on each market):

marketOperations object

The succession of user trades within a located polygon (for example, Buy bch_usd->Sell bch_btc->Sell btc_usd).

The following data is displayed for each of these trades:

amount number

The order amount.

lastOrderDate string

The date and time when the order has last been updated.

instrument string

The currency pair identifier (such as btc_usdt): {baseAsset}_{quoteAsset}.

orderSide string

The order side: Buy or Sell.

RESPONSE EXAMPLE 
[
  {
    "email": "alice@mailinator.com",
    "arbitrage": {
      "Buy bch_usd->Sell bch_btc->Sell btc_usd": [
        {
          "amount": 1,
          "lastOrderDate": "2021-02-11T12:56:20.876671Z",
          "instrument": "bch_usd",
          "orderSide": "Buy"
        },
        {
          "amount": 1,
          "lastOrderDate": "2021-02-11T12:56:01.425742Z",
          "instrument": "bch_btc",
          "orderSide": "Sell"
        },
        {
          "amount": 1,
          "lastOrderDate": "2021-02-11T12:56:15.115638Z",
          "instrument": "btc_usd",
          "orderSide": "Sell"
        }
      ]
    }
  }
]