-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
real-time all symbol price monitoring #13
Comments
@pavlexander, my plan is to support all official functionality. There is official support for All Market Tickers Stream. I just recently incorporated this functionality into |
@sonvister it is not working correctly for me, unfortunately.
The non-web-socket version prints out the data correctly, however, the real-time version of it is either showing results several times and stops, or not showing any results at all no matter how many times I restart the application.. For the sake of testing I have created several output methods:
I was trying to use array results (evt.Statistics) as it is, and as IEnumerable (hence the evt.Statistics.AsEnumerable() in the code), with no success. |
@pavlexander, for debugging the sample application you can refer to the |
Thank you. I didn't know about the log.. Yes, this seems to be the same issue as I have in my log as well! |
For now, I have commented-out the check (allowing for the invalid trade counts). I also modified |
Is there an API to monitor prices for all symbols real-time?
For example, when you open up the main page (href: /) then there is a new WebSocket connection established:
which seems to be monitoring price changes for all currencies simultaneously. Output format for each currency is:
Unfortunately, I can not find the websocket endpoint in the official list of endpoints and so I could not find an API in this binance project which would provide a similar kind of results.
So my question is - is there support for this functionality planned, if not, then what would be the best approach to get this data real-time?
I can of course spam GetPricesAsync API but then that would certainly not be a correct way of doing it..
The text was updated successfully, but these errors were encountered: