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_
• ...

[M3tz3l]

@oliver-zehentleitner done

[oliver-zehentleitner]

could you provide a list of what is not covered from you PR? So we know what we have to finish later.

[oliver-zehentleitner]

There is also a testnet: wss://dstream.binancefuture.com'

[M3tz3l]

What is missing are the websocket user data requests and coin-m futures testnet support. Would it make sense to create separate issues?

[oliver-zehentleitner]

Cool, the public streams are all supported? Generated payloads are all working?

I think one thread/issue is enough.

[jackisdesigning]

Any thought on the coin-m futures websocket user data requests and the testnet support?

[Indiana3714]

does the stream 'aggTrade' seem to work for anyone?

I tried this from the example ".create_stream(['aggTrade'], {'btcusd_perp', 'ethusd_perp', 'bnbusd_perp'})" together with "BinanceWebSocketApiManager(exchange="binance.com-coin-futures")"

but have never gotten back any valid response from the stream buffer.

[jlixfeld]

Here's a supported example you can try.

https://github.com/oliver-zehentleitner/unicorn-binance-websocket-api/blob/master/example_binance_coin_futures.py

[Indiana3714]

Thanks for the example but I've run it, commented out all the lines after "aggTrade" and this is my output:

[oliver-zehentleitner]

@Indiana3714 I recommend starting a new issue! This topic does not have anything to do with adding the new endpoints :)

And I would need the infos that we ask on a new bug report.... for example: which websockets version do you use and which ubwa version?

[Indiana3714]

@Indiana3714 I recommend starting a new issue! This topic does not have anything to do with adding the new endpoints :)

And I would need the infos that we ask on a new bug report.... for example: which websockets version do you use and which ubwa version?

Okay thanks oliver, I've made one here https://github.com/oliver-zehentleitner/unicorn-binance-websocket-api/issues/208