Some order request weights are counted as regular request weights

API Futures API
,
1

Hello,

as I understand, when I send some order request, in its response header should be property X-MBX-ORDER-COUNT-**, but it’s not happening with these requests:

  • DELETE /fapi/v1/allOpenOrders
  • DELETE /fapi/v1/batchOrders
  • DELETE /fapi/v1/order
  • POST /fapi/v1/batchOrders
  • POST /fapi/v1/countdownCancelAll

I also tested, that header is not just missing, but it isn’t counting order weight at all, instead, these requests are counted as X-MBX-USED-WEIGHT.

PS: I am testing this on the Binance Futures Testnet.

2

X-MBX-ORDER-COUNT-** only used for placing order endpoints, DELETE action doesn’t returns this usage, that’s correct.

3

I see, thank you! So endpoints that should have header X-MBX-ORDER-COUNT-** are only these ones?

  • POST /fapi/v1/batchOrders
  • POST /fapi/v1/countdownCancelAll
  • POST /fapi/v1/order
4 
POST /fapi/v1/countdownCancelAll

is not an order endpoint. It count towards normal request weight.

2 Likes
5

yes, under category of “Cancel order” :slight_smile:

1 Like