-
Notifications
You must be signed in to change notification settings - Fork 767
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
Binance API Deprecation [effective on Septembre 9th!] #491
Labels
Comments
gunar
added a commit
to gunar/node-binance-api
that referenced
this issue
Sep 8, 2020
Fixes jaggedsoft#491 Ideally this would warrant a breaking change of the library but since the new endpoint returns a subset that is consistent with previous behavior, and understanding the risk assessment of letting thousands of consumers of the library have their applications be broken, it seems smart to pipe one stream into the other.
Reminder that we've deprecated |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per Binance API announcement,
![Screenshot from 2020-09-07 15-23-48](https://user-images.githubusercontent.com/47316824/92392706-f6ca7e00-f11e-11ea-94e4-a70f35eaabb7.png)
outboundAccountInfo
data stream is now deprecated.But looking at
![Screenshot from 2020-09-07 15-29-14](https://user-images.githubusercontent.com/47316824/92392688-ee724300-f11e-11ea-81ac-e41f1be9d08b.png)
node-binance-api
source code, the deprecated type is still in use, and the new typeoutboundAccountPosition
is not used.What is the recommended way to handle this API change? (effective in 2 days)
Thanks!
The text was updated successfully, but these errors were encountered: