This repository has been archived by the owner on Feb 23, 2022. It is now read-only.
Added support to Futures-API #37
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello Charles Craysiii,
First I would like to thank you and the contributors for the excellent work of the code in the repository.
Following a small contribution to support Futures-API:
https://binance-docs.github.io/apidocs/futures/en/
The changes I made are working correctly.
Just not sure if it would be possible to do it in a simpler way.
Could you review if them are in accordance with your good practices?
ps: now the endpoints are correct and working.
Thanks!