Binance Is Deleting Old API Keys. What to Do? + ByBit Update
Binance has notified a lot of users about removing old non-whitelisted API-keys.
How to solve the issue?
- The solution is quite simple, you need to create a Tax Report key on the exchange website (this key is no different from any other, except that it is always "read-only" and there are no other options).
2. After creating this key, open the "My API keys" page on the TMM website and click edit your current API key by clicking on the Pencil and paste your key.
Done, the journal itself recognizes the new key and reconnects.
Another way to solve the problem is to add whitelist all IPs:
18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52
184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52
P.S.: What to do if there is an error?
You might have mixed up the exchange's accounts. You can edit the key only if the account on the exchange remains identical.
🔥 We are also happy to announce that we have expanded the options for ByBit users, and now our journal supports ByBit Inverse Futures.