Adding new endpoint wss://dstream.binance.com - perpetual coin futures

[oliver-zehentleitner]

The base endpoint is: wss://dstream.binance.com

https://binance-docs.github.io/apidocs/delivery/en/#change-log

Special handling for userData streams

Websocket Request for user data:
    <listenKey>@account request for user's account information
    <listenKey>@balance request for user's account balance
    <listenKey>@balance request for user's position information

[oliver-zehentleitner]

Request: User's Position
<listenKey>@position

[coinabc123]

Hi, any updates?

[xiandong79]

any updates?

[oliver-zehentleitner]

No :/

[M3tz3l]

What's the exact problem here @oliver-zehentleitner with the listenkey handling?

[oliver-zehentleitner]

Its not a problem, its just not the same as the other private channels.

Now there are 3 types, the handling has to get extended.

[M3tz3l]

I tested a little and by just changing the futures websocket baseurl to dstream and the enpoint to dapi I can receive the update events just like with USDT margined futures. The new streams are just optional. For me personally, this would be enough for now and should only be small effort. I could open a PR for that if you agree.

[M3tz3l]

One can then receive all market data streams and update events via user data stream and extend with support for user data requests later.

[oliver-zehentleitner]

@M3tz3l yes that would be great! could you please also provide an example file with tests what is working and what not?

Docs: https://binance-docs.github.io/apidocs/delivery/en/#websocket-market-streams

For example "btcusd_200925@depth" or "btcusd_200925@aggTrade" does a subscription to it work?

• @markprice OR @markprice@1s
• @markprice OR @markprice@1s
• @indexPrice OR @indexPrice@1s
• @continuousKline
• @indexPriceKline_
• ...