We have released the following improvements and bug fixes to the Clover Sandbox and Production environments:
Concurrent Rate Limiting
Some of Clover's API endpoints are more resource-intensive than others. Multiple retry requests to such endpoints can add more demand to already overloaded resources.
We have introduced concurrent rate limiting to create more mindful and efficient use of our API. You can find detailed information about concurrent rate limiting in our Developer Guidelines.
While our existing rate limits are set for the number of API requests you can make per second, we have set concurrent rate limits for the number of in-progress API requests you can have at the same time.
The following table shows the limits that we have in place:
Concurrent Rate Limit
50 per second
16 per second
Our bug fix makes webhooks more robust. If an app is installed with a registered webhook, the webhook is triggered every time as expected.
If you have any questions, please use Clover Community.
To receive more 3rd party developers communication from Clover, sign up here.
Updated over 2 years ago