The resource loading... loading...

Summary of futures exchange orders and hold interface query details

Author: Inventors quantify - small dreams, Created: 2024-08-21 13:48:02, Updated: 2024-08-22 09:49:06

Adding the various futures exchanges GetOrders / GetPositions related interfaces, the current futures exchanges are 19 + 2 ((new addition) = 21 and there are currently 56 exchanges in total.

GetOrders

  • futures_Aevo
    No distinction between contract types

  • The future of Apollo X No distinction between contract types

  • futures_Bibox_v3
    Not supported

  • futures_binance
    Different paths according to unified account/non-unified account distinction/U-base/currency base/option distinction; option page query;

  • futures_bitfinex
    No distinction is made between types of contracts;

  • futures_bitget_v2
    Page-separated query; based on parameter differentiation of currency denomination/U denomination

  • futures_BitMEX
    Page queries; no distinction between contract types

  • futures_bybit_v5
    Page queries; specified parameters based on U-bit/coin-bit/option differentiation

  • futures_CoinEx
    Page queries; no distinction between contract types

  • futures_crypto_com
    No distinction is made between types of contracts;

  • futures_deribit_v2
    The contract code parameter must be specified;

  • futures_gateio
    Split-page query; options are a separate path based on the different paths of the persistent/delivery/settlement currencies; Requests >= 2 times

  • futures_hbdm
    Page-by-page query; different paths are distinguished according to factors such as full stock/by-stock/permanent/delivery/coin base/U base. Requests >= 2 times

  • futures_kraken
    No distinction is made between types of contracts;

  • futures_KuCoin
    Page queries; no distinction between contract types

  • futures_MEXC
    Partition query; does not distinguish between contract type, specify a contract parameter written in path.

  • futures_okex_v5
    Page queries; query parameters that differentiate between permanent, assignment, and option Requests >= 2 times

  • futures_WOO
    Page queries; no distinction between contract types

  • futures_dYdX
    Page queries; no distinction between contract types

  • futures_BitMart
    No distinction between contract types

  • futures_Digifinex
    Page queries; no distinction between contract types

GetPositions

  • futures_WOO
    The interface has no parameters and does not distinguish between contract types; quoteCurrency: map[USDT:true]

  • futures_okex_v5
    Query parameters distinguish between permanent, delivery, option;quote Currency: map[USD:true USDC:true USDT:true] Requests >= 2 times

  • futures_MEXC
    The interface has no parameters and does not distinguish between contract types; quoteCurrency: map[USD:true USDT:true]

  • futures_KuCoin
    The interface has no parameters and does not distinguish between contract types; quoteCurrency: map[USD:true USDC:true USDT:true]

  • futures_kraken
    No distinction is made between contract types; quoteCurrnecy: map[USD:true], the exchange is more special, quoteCurrency only USD symbol There is a mixed underwriting perpetuity contract, a regular perpetuity contract, and the quote Currency is USD

  • futures_hbdm
    Different paths are distinguished according to factors such as full position/one-by-one/permanent/delivery/coin base/U base. Requests >= 2 times

  • futures_gateio
    Only perpetual contract page queries; options contracts must explicitly contain contract code, do not support getting all; options are separate paths based on different perpetual/delivery/settlement currency paths; quoteCurrency: map[USD:true USDT:true] Requests >= 2 times

  • futures_dYdX
    Page queries; no distinction between contract types; only USD pairs

  • futures_Digifinex
    No distinction is made between contract types; quoteCurrency: map[USD:true]

  • futures_deribit_v2
    The currency parameter specifies the currency (specified in U-bits, currency-bits); the kind parameter classifies options, futures; the kind parameter distinguishes between ordinary contracts and composite contracts; quoteCurrency: map[USD:true USDC:true USDT:true]

  • futures_crypto_com
    No distinction is made between contract types; quoteCurrency: map[USD:true]

  • futures_CoinEx
    No distinction is made between contract types; quoteCurrency: map[USD:true USDC:true USDT:true]

  • futures_bybit_v5
    Page query; specify parameters based on U-bit/coin-bit/option distinction; quoteCurrency: map[USD:true USDC:true USDT:true]

  • futures_BitMEX
    No distinction is made between contract types; quoteCurrency: map[ETH:true EUR:true USD:true USDC:true USDT:true XBT:true XXX:true]

  • futures_BitMart
    No distinction is made between contract types; quoteCurrency: map[USD:true]

  • futures_bitget_v2
    Currency: map[SUSD:true SUSDC:true SUSDT:true USD:true USDC:true USDT:true]

  • futures_bitfinex
    No distinction is made between contract types; quoteCurrency: map[BTC:true TESTUSDT:true UST:true]

  • futures_binance
    Different paths depending on unified account/non-unified account differentiation/U base/currency base/options; quote Currency: map[BTC:true USD:true USDC:true USDT:true]

  • futures_Bibox_v3
    The U-bit/coin-bit path varies; quoteCurrency: map[USD:true USDT:true]

  • futures_ApolloX
    No distinction is made between contract types; quoteCurrency: map[USDT:true]

  • futures_Aevo
    No distinction between contract types; quoteCurrency: USDC only


More