-
Notifications
You must be signed in to change notification settings - Fork 767
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
node-binance-api-testnet - binance.openOrder(false, (error, openOrders) => ... throwing Invalid API Key for testnet #787
Comments
Ive tried generating a brand new HMAC from the website, and the same thing is still happening |
can confirm that same code works on the mainnet and also that if I use the node-binance-api library, with the testnet credentials, this also does not work, |
is this library working? |
it's years out of date. find the official binance one. it's a bit of apita.
I've stopped using binance because their customer service and support is
just... big business lazy rubbish
…On Mon, 7 Mar 2022, 22:57 Elio Suárez Santana, ***@***.***> wrote:
is this library working?
—
Reply to this email directly, view it on GitHub
<#787 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB2PPWQATHJG3WTRWJIU23U62CVBANCNFSM5LQ6Q5FQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
for that APIKEY and APISECRET, I can get read data sockets for everything, for the testnet data,
When I call
binance.openOrders(false, (error, openOrders) =>...
there are currently no open orders (I havent yet tried to open any
openOrders is
{}
The text was updated successfully, but these errors were encountered: