Sub-Account

Futures Position-Risk of Sub-account V2 (For Master Account)

Changed on Sep 19, 2023

Weight(IP): 1

get/sapi/v2/sub-account/futures/positionRisk

Request

Base URL
https://api.binance.com
URL
https://api.binance.com/sapi/v2/sub-account/futures/positionRisk
Auth
API key in header X-MBX-APIKEY

Query parameters

emailstring required

Sub-account email

futuresTypeinteger required

Example:1

1 - USDT Margined Futures
2 - COIN Margined Futures

recvWindowinteger

Example:5000

The value cannot be greater than 60000

timestampinteger required

UTC timestamp in ms

signaturestring required

Signature

Response

USDT or COIN Margined Futures Position Risk

Example response

{
  "futurePositionRiskVos": [
    {
      "entryPrice": "9975.12000",
      "leverage": "50",
      "maxNotional": "1000000",
      "liquidationPrice": "7963.54",
      "markPrice": "9973.50770517",
      "positionAmount": "0.010",
      "symbol": "BTCUSDT",
      "unrealizedProfit": "-0.01612295"
    }
  ]
}

Changes

Sep 19, 2023558ab69ec555 Revision changes
- breaking
  removed the enum value 1.00 from the query request parameter futuresType
- breaking
  removed the enum value 2.00 from the query request parameter futuresType
Oct 25, 2021a484ce871a72 Revision changes
- breaking
  for the query request parameter futuresType, the format changed from no format to int32
- breaking
  for the query request parameter recvWindow, the format changed from no format to int64
- breaking
  for the query request parameter timestamp, the format changed from no format to int64
- info
  the response property became required for the status
- info
  the response property became required for the status
- info
  the response property became required for the status
- info
  the response property became required for the status
- info
  the response property //// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property //// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status
- info
  the response property ////// became required for the status

Operation history