-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Develop #722
base: master
Are you sure you want to change the base?
Conversation
Add 1 Month Interval (1M) for Historical Klines
please document a bit clearer on what this pr is trying to achieve. |
Binance launched the API for Vanilla Options in January: https://binance-docs.github.io/apidocs/voptions/en/#general-info |
What's the status of this? I would like to use the API to trade vanilla options, but this wrapper does not offer the functions mentioned by @dragosgr2 - https://binance-docs.github.io/apidocs/voptions/en/#general-info I could dedicate some time, implement it and push PR, if nobody is working on it? |
@faileon further effort would be greatly appreciated. |
When end_ts is passed historical klines are fetched until Binance API returns no results. With every query start_ts is incremented. For the most part this cause one unnecessary query to Binance to be made, where start_ts is bigger than end_ts. Moreover, when fetching klines for future markets (not spot), Binance API returns an error in such condition (-1023). This makes it impossible to fetch klines for future markets when providing end_str param.
Fix passing start_ts > end_ts when fetching historical klines
Can you add the Vanilla Options API from Binance to the client?