Closed CasperNielsen closed 7 years ago
Thanks for your bug report. I see this error occasionally but cannot reproduce this reliably.
Try again (maybe a different time of day) and see if you see that issue again.
https://github.com/Mikadily/poloniexlendingbot/issues/273
I'm going to leave this ticket open and see if I can add a better error message for the 422 error code.
I just started getting this error today also. Keys still work with other apps.
@d-fay @CasperNielsen Could you try creating a new api key/secret? Seemed to work for this person https://github.com/dutu/poloLender/issues/11 and also suggested in https://bitcointalk.org/index.php?topic=1715214.880
@BenjiLee 422 error from my experience is too many API calls too fast. Considering that I am able to use this API key still with a different script, it does not seem to be the API key that is the issue. Instead their API appears to be unhappy with you app. I would venture a guess that your app might make too many sequential calls within a short period of time.
EDIT: I created a new API key and it is currently working again. I recommend spacing out your API calls a bit as well as catching this error and having the app retry again after a period of time.
EDIT: I created a new API key and it is currently working again. I recommend spacing out your API calls a bit as well as catching this error and having the app retry again after a period of time.
The limit is 6 calls/second according to the Poloniex API doc and the max the scripts will call in a succession is 2. If I get closer to the limit of 6, I may consider added some throttling.
I've added an error message for now. https://github.com/BenjiLee/PoloniexAnalyzer/pull/26
I must reiterate that at some point Polo decided it doesn't like your app as the API keys still work just not with this analyzer.
@d-fay Thanks for mentioning that it works with other scripts. I think I know what the issue is. The Poloniex trading api uses a parameter called nonce which needs to be greater int than the last and this number persists on the account. If the script you ran is using a different nonce that what I am using (epoch time) than one of the scripts will get a 422. The script that gets the 422 is the one with the smaller nonce. The only solution here is to create a new API key for this script since each script uses their own system for the nonce parameter.
Is the other script you are using open source? I would like to confirm how they calculate the nonce parameter.
When i try to run the file with the API commands i get this error. It runs fine with the GetChangeOverTime arguments. Have checked my API key / Secret, but it seems fine.
Can you spot the problem?