As shown in the figure, the program that started and stopped the robot through the platform extension API works well. But yesterday, after changing the password, the bot failed to start and shut down. Excluding suspicions: 1st, you need to update the API after changing your passwordIf the password is changed, the API is updated in time, otherwise even the bot that calls the platform extension API will not start, so there is no API failure problem.
2 The robot id is incorrect? Figure 1, the robot starts normally, and the controller prints and calls the API to start
-------------------- Problem solved, friends who are in the pit see
1 The client said to update all the exchanges' api-key, and my exchange is a futures exchange, it is without an api-key, that is, the exchange that calls the bot installed with the extended api needs to update the api-key. That is the diagram below in the instruction documentation. Why do we use wexapp to hang it?
Is it OK to start and stop the robot after 2 changes?
I'm sorry, but the shutdown log will tell you that the password is broken.
Solution: Remove the bot (does it need to be removed? can't directly re-install? you'll know if you try it), create a new bot to re-install once wexapp exchange
The grassAll exchanges need to re-add API-keys, and are alerted when changing their passwords
abc122615I'm not adding my account password again, I've perfected the post.
The grassAlso, add the account password again.
abc122615/upload/asset/10933ec91c2e7dcd2d433.png This is a list of all the different ways Ec91c2e7dcd2d433.png is credited in the database. In this example, the futures exchange does not have an API-key.