Currently, we are resetting the IP daily to avoid the recurrence of the issue of getting error. However, despite this workaround, we are still encountering some cases.
we are trying to solve the issue, and need your support to get this information:
This is covered in the error codes, in the web API docs, and in the more general Account Security article. You can only use API keys from static IP addresses. So, get a static IP address.
We allow up to 3 IP addresses to use an API key. This is configurable (from 0 to 3).
We don't email on failures (*you* however can and should notify yourselves when API calls fail – do it internally).
There are no automatic resets, and any attempts to automatically reset API keys will result in us locking the ability for that account to reset API keys.
We don't like when customers shoot themselves in the foot.
The solution to all of this (stated in multiple places, and now here again): use a static IP address.