Positions zero-valued parameters in Future Market

API Futures API
, ,
1

During last night around 3:46:00, we faced a zero-valued parameter for positions information in Future Market’s RestAPI, while the position was open and had values in a GUI panel.

First position log on 2021-04-22T03:46:05.182Z

   {
      "symbol": "DOGEUSDT",
      "leverage": "5",
      "notional": "505.22308200",
      "checkTime": "2021-04-22T03:46:05.182Z",
      "markPrice": "0.27974700",
      "entryPrice": "0.276932",
      "marginType": "isolated",
      "updateTime": 1619063103782,
      "positionAmt": "1806",
      "positionSide": "BOTH",
      "isolatedMargin": "104.91167272",
      "isolatedWallet": "99.82778272",
      "isAutoAddMargin": "false",
      "liquidationPrice": "0.22389533",
      "maxNotionalValue": "250000",
      "unRealizedProfit": "5.08389000"
    }

Second Position value at 2021-04-22T03:46:16.351Z

    {
      "symbol": "DOGEUSDT",
      "leverage": "5",
      "notional": "0",
      "checkTime": "2021-04-22T03:46:16.351Z",
      "markPrice": "0.28032810",
      "entryPrice": "0.000000",
      "marginType": "isolated",
      "updateTime": 1618937624178,
      "positionAmt": "0",
      "positionSide": "BOTH",
      "isolatedMargin": "0.00000000",
      "isolatedWallet": "0",
      "isAutoAddMargin": "false",
      "liquidationPrice": "0",
      "maxNotionalValue": "250000",
      "unRealizedProfit": "0.00000000"
    }

This caused many issues in our systems, and we had to spot our trading system.

Did you face the same issue last night?
What should I do in these cases?

2

Hello, it’s possible that /fapi/v2/positionRisk had a hiccup at the mentioned time, it’s all stable now.

As a recommendation, you might want to use websocket (https://binance-docs.github.io/apidocs/futures/en/#event-balance-and-position-update) to not frequently send requests to check the position updates, avoiding reaching the IP requests limit.

1 Like