How to fetch a FULL order status about node-binance-api HOT 10 CLOSED

Above code didn't work even now. I get following error:
ERROR: "{\"code\":-1104,\"msg\":\"Not all sent parameters were read; read '5' parameter(s) but was sent '6'.\"}"

from node-binance-api.

@jaggedsoft I didn't quite get it. The documentation mentions it in newOrder creation API and not in orderStatus. But you have added this in orderStatus(as mentioned by you in above code snippet) and order status can only be checked for an order which was already placed. And once the order is completed then only there can be any use of FULL to check the details of the fills. There seems to be ambiguity in the documentation and actual implementation?
My requirement is to fetch the details of order fills, as i ultimately need the 'price' at which the order gets executed. using orderStatus i can get it by taking weighted avg of price and qty. Is there any other way of fetching the 'price'?

from node-binance-api.

Right now it only supports symbol, orderid
I'll add the rest of the flags tonight

from node-binance-api.

Thanks for the report!

from node-binance-api.

The orderStatus function now supports newOrderRespType

orderStatus: function(symbol, orderid, callback, flags = {}) {
    let parameters = Object.assign({symbol:symbol, orderId:orderid}, flags);
    signedRequest(base+'v3/order', parameters, function(error, data) {
        if ( callback ) return callback.call(this, error, data, symbol);
    });
},

I'll update when the release is live

from node-binance-api.

binance.orderStatus(_SYMBOL_, orderID, function(err, orderStatus, symbol) {
       if(err)
         logger.info(`ERROR: ${err.message}`);
       else{ 
         logger.info(symbol + " order status:" + JSON.stringify(orderStatus));
       }
}, {newOrderRespType: 'FULL'});

from node-binance-api.

Available now in v0.4.11

from node-binance-api.

newOrderRespType, as its name implies, must unfortunately only be available in new orders

from node-binance-api.

@jaggedsoft any update on this?

from node-binance-api.

I'm afraid not, it appears the deficiency is on the binance side
But I can suggest they provide what you're after

It's also possible that one of these may provide what you want. But I'm not sure the difference between them yet

Recent Trades (historicalTrades, recentTrades, aggTrades functions)

binance.aggTrades("BNBBTC", {limit:500}, (error, response)=>{
	console.log("aggTrades", response);
});

binance.recentTrades("BNBBTC", (error, response)=>{
	console.log("recentTrades", response);
});

binance.historicalTrades("BNBBTC", (error, response)=>{
	console.log("historicalTrades", response);
});

from node-binance-api.