KUCOIN API UpGRADE PROBLEM

Gunbot Shop Gunbot Forum Technical Support KUCOIN API UpGRADE PROBLEM

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #12476
    Paul Halliday
    Participant

      Hi I received a notification from Kucoin to upgrade my V2 API key to V3.  In Kucoin website I created a v3 key and entered (by overwriting the V2 details) the details in my Gunbot exchange settings tab.  Gunbot gives a message “API credential wrong – Cannot connect” and I can’t set further – how do I upgrade my API from V2 to V3 .

      #12483
      Paul Halliday
      Participant

        Ok so this has been a disaster. I now have to do a fresh install and am upgrading from V24 to V29. However I just can not past the exchange api screen I can not delete the 2 old exchanges no longer used and the exchange I do use Kucoin still requires me to upgrade the API key from v2 to v3 and I can not get the gunbot set up wizard to accept the new key  – any ideas Error screen

        #12486
        Aitor
        Keymaster

          Hi Paul, send me via PM your gunthy wallet you want to edit, the old api and the new api you need to set, and I will change it for you. Then with one working api, you will be able to do any change yourself.

          #12489
          Paul Halliday
          Participant

            PM sent

            #12498
            Paul Halliday
            Participant

              Can anybody help me please – I have been unable to use for quite a while now and am totally stuck

              #12502
              Aitor
              Keymaster

                Sure, I already answered your PM.

                #12585
                JohnHenry
                Participant

                  Make sure your V3 API key has the correct permissions on Kucoin. After updating your API key in Gunbot, double-check both the API key and secret. If the error persists, try regenerating the V3 key and re-entering it in Gunbot’s settings. If the issue continues, consider reaching out to Gunbot support to ensure compatibility with the new API version.

                Viewing 7 posts - 1 through 7 (of 7 total)
                • You must be logged in to reply to this topic.
                Contact us