Shu Wang

Maybe there is some history about this API, since python-binance split this API into two methods: `get_orderbook_ticker()` and `get_orderbook_tickers()`. The plural form will call `ticker/bookTicker` API without any param, while...

`LIMIT_MAKER` is not used in futures order. For post only orders, set timeInForce to `GTX`.

It could be done by subscribe diff book depth stream. I believe binance has described this well in their official document: [partial-book-depth-streams](https://binance-docs.github.io/apidocs/futures/en/#partial-book-depth-streams) The `How to manage a local order book...

Why don't you print the message first and check the content? Anyway the result is expected and indeed there is no key `'e'` in `msg`.

https://www.binance.com/en/support/faq/c-4?navId=4#18-62 https://binance-docs.github.io/apidocs/futures/en/#new-order-trade Only when closing position can one set such order to be triggered. To open position, one needs to track orderbook or latest price from websocket API manually.

Not yet. Check [Endpoints.md](https://github.com/sammchardy/python-binance/blob/master/Endpoints.md) to find out whether an endpoint is implemented or not.

duplicate to #1174

I can confirm this bug. Same problem with #1174 . Have found a quick fix there, but no promise since I don't use threaded socket.

Method starts with `futures_coin` is for coin-m futures, not usd-m futures. Check exchange_info api for the right symbol name.

Sorry, cannot reproduce. Don't know why your web page shows wrong data. My screenshot:  The prices exactly matches the candles in your image. ( note: I'm in GMT+8 timezone...