Hello,
@peter maybe those limitations have to be added in the API documentation, because the issue on lego was a bit surprising to me.
I’m sure that you have reasons behind this rate limit, but 200ms is very slow from the point of view of an HTTP client and for a DNS API.
Also this kind of rate limiting per second can be an issue with concurrency calls or multiple API clients: in this case it’s impossible to sleep 200ms between two calls.
Could you explain this rate limit per second instead of only a rate limit per minute and per hour?