-
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
use ccxt as exchange connector to open up a whole lot more exchanges #54
Comments
Yes, CCXT could be a good choice for simplifying the setup part and integrating with a lot more exchanges... I am wondering though, if ccxt enforces a unique response format? (As format usually changes from each exchange, and that's kinda the main challenge that we are facing here) |
ccxt has some functions which are implemented for all exchanges, and returns with the same structure. other unique api endpoints are reachable too but not standardised. try it, it is really easy to get started with. |
https://github.com/ccxt/ccxt
ccxt is an actively developed robust api wrapper, it would be worth to use to implement other exchanges fast
The text was updated successfully, but these errors were encountered: