API-Impacting Changes Following Unified Wallet Upgrade

Written by BTSE

August 7, 2024

Dear Traders,

We would like to inform our users of API-impacting changes once an account has been upgraded to the Unified Futures Wallet

Firstly, please note that all traders will have to upgrade to the Unified Futures Wallet eventually. Starting September 4, traders’ wallets will be automatically upgraded in batches over the course of two months. This is done to simplify the management of your futures trades and improve the user experience. All of your futures-related assets and trades will be consolidated into one wallet, but you will be able to toggle between Isolated and Cross modes for each asset. 

Users can get a head start by upgrading the Unified Futures Wallet on the Wallets screen on the BTSE interface. Click here for the full guide.

Secondly, for API traders already connected to BTSE, after you upgrade to the Unified Futures Wallet, certain APIs will change and the way you interact with them will have to change, i.e. the commands and symbols that you input will have to change, and some of the resulting outputs will change. (Please see below)

We ask that all API traders review the changes in full below before they upgrade to the Unified Futures Wallet. 

Please note:

The criteria for automatic upgrading are as follows: Users must have no active positions, no open orders, and no active Futures Grid Trading Bots.

(If you have an open position, we will not upgrade your wallet until all positions are closed)

Please note that these changes are enacted to improve your trading experience on BTSE. If you have any further questions, please contact us at support@btse.com. Thank you for understanding.

 

Migration Notes from v2.1 to v2.2

  • All the symbol fields in request should use XXX-PERP. 
    • Example: BTC-PERP
  • All symbol fields in responses will change from XXXPFC to XXX-PERP. 
    • Example: BTCPFC → BTC-PERP
  • All market fields in responses will change from XXXPFC-USD to XXX-PERP-USDT. 
    • Example: BTCPFC-USD → BTC-PERP-USDT 
  • All wallet name fields in responses will change from ISOLATED@XXXPFC-USD to ISOLATED@XXX-PERP-USDT. 
    • Example: ISOLATED@BTCPFC-USD → ISOLATED@BTC-PERP-USDT 
  • Quote currency field in responses will change from USD to USDT.
  • Change the response content of the API [`Get Leverage`] to an array.

 

Before

{

  “symbol”: “BTC-PERP”,

  “leverage”: 100.0,

  “marginMode”: “ISOLATED”

}

 

After

[

  {

    “symbol”: “BTC-PERP”,

    “leverage”: 10,

    “marginMode”: “ISOLATED”,

    “positionDirection”: “LONG”

  },

  {

    “symbol”: “BTC-PERP”,

    “leverage”: 3,

    “marginMode”: “ISOLATED”,

    “positionDirection”: “SHORT”

  }

]

  • Once the user upgrades to a unified futures wallet, v2.1 APIs can no longer be used. 

 

v2.2 migration APIs list (Empty Response = Unchanged)

Method Path Request Response
GET /api/v2.2/market_summary symbol symbol
GET /api/v2.2/ohlcv symbol  
GET /api/v2.2/price symbol  
GET /api/v2.2/orderbook symbol  
GET /api/v2.2/orderbook/L2 symbol  
GET /api/v2.2/trades symbol symbol
GET /api/v2.2/funding_history symbol symbol
POST
/api/v2.2/order
symbol
symbol, position id
/api/v2.2/order/peg
GET /api/v2.2/order   symbol
PUT /api/v2.2/order symbol symbol, position id
DELETE /api/v2.2/order symbol symbol, position id
GET /api/v2.2/user/open_orders symbol symbol, position id
GET /api/v2.2/user/trade_history symbol symbol, wallet, position id
GET /api/v2.2/user/positions symbol symbol, position id
POST /api/v2.2/order/close_position symbol, position id symbol, position id
GET /api/v2.2/risk_limit symbol symbol
POST /api/v2.2/risk_limit symbol symbol
POST /api/v2.2/leverage symbol, position id symbol
GET /api/v2.2/leverage symbol symbol
POST /api/v2.2/settle_in symbol, position id  
GET /api/v2.2/user/fees symbol symbol
POST /api/v2.2/order/bind/tpsl symbol, position id symbol, position id
GET /api/v2.2/position_mode symbol symbol
POST /api/v2.2/position_mode symbol symbol
GET /api/v2.2/user/margin_setting symbol symbol
GET /api/v2.2/user/wallet wallet wallet, active wallet name
GET /api/v2.2/user/wallet_history wallet wallet
GET /api/v2.2/user/unifiedWallet/margin symbol symbol, active wallet name
GET /api/v2.2/user/margin symbol wallet
POST /api/v2.2/user/wallet/transfer wallet related field active wallet name, wallet
POST /api/v2.2/subaccount/wallet/transfer wallet related field  

 


Our aim is to create a platform that offers users the most enjoyable trading experience. If you have any feedback, please reach out to us at support@btse.com or on X @BTSE_Official.

Note: BTSE blog content is intended solely to provide varying insights and perspectives. Unless otherwise noted, they do not represent the views of BTSE and should in no way be treated as investment advice. Markets are volatile, and trading brings rewards and risks. Trade with caution.

Related Articles

Stay Informed with BTSE

Join Our Newsletter

Never miss a beat with the latest updates and industry insights from BTSE.

Follow Us

Join our rapidly growing community and exclusive events!