-
Notifications
You must be signed in to change notification settings - Fork 217
[OKEX] Support for API v3 #242
Comments
I recommend a similar approach to #205 - essentially deprecate the old api and produce a new api, under a new package/project for v3 |
Okex has set the deadline. See https://support.okex.com/hc/en-us/articles/360021935351
|
I assume you mean #261, @Flemingjp. I guess there are no developer/users of xchange-stream that use Okex, otherwise we would have seen a PR to fix this. If anyone needs this, a bounty may help - make it worth someone's while. |
Essentially yes, I believe a bounty is the way to go with this - as it essentially seems to be few users and fewer developers using this exchange |
Whats the status of this? I have 80% of OkEx working on the v3 api - happy to provide the code |
Is OKEX code still broken? It would be nice to remove it from README in such a case to prevent users to spend time for integration with the broken code.. |
OKEx has launched their new version of API (v3). Although API v3 and v1 are currently both supported, API v1 will be totally removed someday in the future. So the support for API v3 needs to be added into this repo.
The text was updated successfully, but these errors were encountered: