The resource loading... loading...

Problems with the batch orders API of the Binance contract

Author: High suction low throw, Created: 2020-05-11 19:35:46, Updated:

In the Debugging Toolhttps://www.fmz.com/m/debug

I tried all sorts of ways to order from the Binance contract batchOrders API, and all failed.

Failed to build url according to discussion content searched below

https://github.com/ccxt/ccxt/issues/6805


function main() {
        exchange.SetContractType('swap')
        var makeOrders = [
                           {"symbol":"BTCUSDT","side":"BUY","type":"MARKET","quantity":0.002},
                           {"symbol":"LTCUSDT","side":"BUY","type":"MARKET","quantity":0.002}
                         ]
        params = []
        for (var i = 0; i < makeOrders.length; i++) {params.push(encodeURI(JSON.stringify(makeOrders[i])))}
        params = "batchOrders=["+params.join(",")+"]"
        Log(params)
        var allOrders = exchange.IO('api', 'POST', '/fapi/v1/batchOrders',params);
        Log(allOrders)
}

This is a list of all the different ways [code:400,msg:null}, {code:400,msg:null} is credited in the database.

According tohttps://www.fmz.com/apiThe insideexchange.IOThe explanation still fails


function main() {
        exchange.SetContractType('swap')
        var makeOrders = {
                          "batchOrders":[
                                          {"symbol":"BTCUSDT", "side":"BUY" , "positionSide":"LONG" , "type":"MARKET", "quantity":0.001},
                                          {"symbol":"BTCUSDT","side":"SELL","positionSide":"SHORT","type":"MARKET","quantity":0.001}
                          ]
        }
        var allOrders = exchange.IO('api', 'POST', '/fapi/v1/batchOrders',"",JSON.stringify(makeOrders));
        Log(allOrders)
}

Tip: Futures_Binance error Futures_OP 4: 400: {timestamp:1589196850717,path:"/fapi/v1/batchOrders",msg:System error}

Is there any problem with the Bitcoin contract batchOrders API and how should I construct parameters?

Thank you.


More

High suction low throw/fapi/v1/order using the raw parameter also failed, but using the params method is normal I'm not going to tell you. function main (() { Exchange.SetContractType (('swap') is the name of the This is a list of all the different ways BTCUSDT is credited in the database. Params = [] var allOrders = exchange.IO (('api', 'POST', '/fapi/v1/order',"",JSON.stringify ((makeOrders))); Log ((all Orders) I'm not sure. I'm not going to. The following is a list of all the different ways Futures_Binance is credited in the database:

High suction low throwUnidirectional, bidirectional, bidirectional orders cannot be placed

Inventors quantify - small dreamsYes, the binary documentation is written as a numeric type, but the numeric type is incorrect, and the strings are all correct.

High suction low throwThe test is available, but there's a small problem with the parameters. "quantity": "0.001" is normal, "quantity": 0.001 failed, i.e. must be toString before amount, not found in other interfaces function main (() { Exchange.SetBase (https://testnet.binancefuture.com) Exchange.SetContractType (('swap')) is a contract type that is used for the exchange of contracts. var is equal to 0.001 What do you mean? var theOrder ={"symbol": "BTCUSDT", "side": "BUY", "positionSide": "LONG", "type": "MARKET", "quantity": amount} // theOrder = exchange.IO (("api", "POST", "/fapi/v1/order", "", JSON.stringify ((theOrder)) // is normal What do you mean? var theOrder = { "batchOrders": {"symbol": "BTCUSDT", "side": "BUY", "positionSide": "LONG", "type": "MARKET", "quantity": amount} I'm not going anywhere. I'm not sure. What do you mean? theOrder = exchange.IO (("api", "POST", "/fapi/v1/batchOrders", "", JSON.stringify ((theOrder)) // Failed Log ((the Order)) I'm not sure.

Inventors quantify - small dreamsIn addition to the upgraded version, the most recent host can be downloaded and used, with the following examples: What's up? function main (() { /* Ordered in bulk This is the same thing. "batchOrders": "symbol": "BTCUSDT", "side": "BUY", "PositionSide": "LONG", and then "LONG", and then "LONG". "type": "LIMIT", and "quantity": "0.001", "Price": "8000", and "Price" is the same as "8000". TimeInForce: "GTC" is the name of the game. I'm not sure. {pos (192,210) } "symbol": "BTCUSDT", "side": "BUY", "PositionSide": "LONG", and then "LONG", and then "LONG". "type": "LIMIT", and "quantity": "0.001", "Price": "8000", and "Price" is the same as "8000". TimeInForce: "GTC" is the name of the game. I'm not sure. I'm not sure. I'm not sure. var ret = exchange.IO (("api", "POST", "/fapi/v1/batchOrders", "", JSON.stringify ((obj)))) Log (("ret:", "ret") is the name of the game. */ What do you think? /* Withdrawal of lot This is the same thing. "symbol": "BTCUSDT", "orderIdList": ["3873637971", "3873637970"] This is a list of all the order IDs in the world. I'm not sure. var ret = exchange.IO (("api", "DELETE", "/fapi/v1/batchOrders", "", JSON.stringify ((obj)))) is the name of the file. Log (("ret:", "ret") is the name of the game. */ What do you think? Sleep ((1000) is the Log ((exchange.GetOrders)) I'm not sure. What's up? I've already tested it and it's fine.

The grassThe weight of the bulk order is five times higher than the weight of the individual order, but it is not necessary in terms of frequency.

High suction low throwI looked at https://www.fmz.com/api exchange.IO (((Exchanges that support raw parameters, with binary contracts But I'm also using params. batchOrders API, using the order api one by one, oh

High suction low throwPraise and worship

The grassI'm not sure if it's upgraded yet, but it should be updated today.

The grassBinance should not support this approach, the documentation says.

High suction low throwI'm using MARKET, the parameters should be enough, it's normal to pass params (that's your code), but it fails to pass raw. This is a list of all the different ways Exchange.IO is credited in the database.

The grassIf you look carefully at the documentation, the parameters are not complete. What's up? In addition to the above-mentioned features, there is also a new feature called "Symbol+Symbol+" which is available in the following format: What's up?