error: ['EAPI:Invalid key'] doing fetchBalance for Kraken
See original GitHub issueUsing Node.JS 8.1.4 I receive this error after instantiation with the api key and private key from Kraken.
const market = new ccxt[key]({
apiKey: data.apiKey,
secret: data.secret
})
console.log(await market.fetchBalance())
Public functions seem to work fine.
Issue Analytics
- State:
- Created 6 years ago
- Comments:23 (13 by maintainers)
Top Results From Across the Web
API error messages - Kraken Support
Invalid signature errors occurs if either your API key or API secret are written incorrectly in your program or because the POST data...
Read more >Invalidkey At Kraken Api With Js, Not With Python - ADocLib
Invalid signature errors occurs if either your API key or API secret are written incorrectly in ... Error: EAPI:Invalid key doing fetchBalance for...
Read more >Kraken EAPI: Invalid key - Stack Overflow
String apiEndpointFullURL = baseDomain + privatePath + endPointName;. After you make that code change, the Invalid Key error should go away. …….
Read more >Getting class kraken not found? ▷ Download ccxt/ccxt +++ without ...
Download ccxt / ccxt / kraken.php - Solve class 'kraken' not found ... <?php namespace ccxt; // PLEASE DO NOT EDIT THIS FILE,...
Read more >kraken.py | searchcode
1# -*- coding: utf-8 -*- 2 3# PLEASE DO NOT EDIT THIS FILE, IT IS GENERATED AND WILL BE ... {"error":["EQuery:Invalid asset pair"]}...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh, sry about my ignorance! I did not know. Let me try 😃
Hi @kroitor, thanks for the assistance 👍
I gerenated a new API key with the following settings:
and the issue seems resolved, thanks! 💯 🥇