-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
fetch_trades reply structure across exchanges #417
Comments
Hi, @vonpupp! Thanks for opening this issue. Looks like GDAX is not parsing the trade result. It will be fixed in 5-10 minutes. Stay tuned! |
Cool, thank you very much for being so responsive. That is just awesome! Kudos. |
It was fixed in 1.9.284+. Don't forget to update it. Thx! |
Great, thanks a lot! I will give it a try and if needed provide some feedback. If you are into algo-trading/bots I would love to share some ideas with you in the future and keep in touch. We are apparently into similar stuff :) |
Is it ok for the data within the |
@vonpupp , yes, the |
Great. Thanks! |
You're welcome! The format and fields recognized for trades are described here: https://github.com/ccxt/ccxt/wiki/Manual#trades-orders-executions-transactions |
Awesome, I saw that a while ago and forgot about it. That helped me out thanks! |
Hi again Kroitor,
I have noticed that when calling the
fetch_trades
method the result doesn't have the same structure across exchanges:When I switch the exchange I am having an exception due to the different hashes (camelcase vs. lowercase). Is this intentional? I guess ccxt does not process the response, but return it in raw, right?
The text was updated successfully, but these errors were encountered: