-
Notifications
You must be signed in to change notification settings - Fork 4k
ALL GDAX Endpoints Deprecated #2517
Comments
Great point. Under the hood Gekko uses a library from coinbase (called gdax) to connect to the exchange. This one needs to be updated first, in that issue tracker I can find some discussion about this: |
It looks like just changing the endpoint in gdax.js from https://api.gdax.com to https://api.pro.coinbase.com works! I'm still testing but it was able to pull up my balance. Just need to see if it trades or have any other issues. |
Thanks! If it all works I would love a PR ;)
…On Thu, Sep 13, 2018 at 10:25 PM, Jack Crypto49er ***@***.***> wrote:
It looks like just changing the endpoint in gdax.js from
https://api.gdax.com to https://api.pro.coinbase.com works! I'm still
testing but it was able to pull up my balance. Just need to see if it
trades or have any other issues.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2517 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA7MD5_L27l-9wKP6JLoflON-Ytz2DmKks5uamq8gaJpZM4Whbtc>
.
--
PGP key at keybase.io/mikevanrossum
<https://keybase.io/mikevanrossum/key.asc>
|
Sure. I just made one. It isn't a permanent fix but hopefully it will buy us a few more months after 12/31/18 as they will eventually update their node.js library with the new branding. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If you feel this is very a important issue please reach out the maintainer of this project directly via e-mail: gekko at mvr dot me. |
@crypto49er, @askmike it's look like it's not working every time #2695 |
https://docs.gdax.com/#deprecation-notice
As of December 31st, everything will break. So what to do now.
Are we already working on this? Is the switch going to involve a lot of code rewriting, or just pointing it to the new coinbase pro endpoint?
The text was updated successfully, but these errors were encountered: