Per the notice from Clover re: API limits at the application level, wanted to check-in on the timing of implementing this.
Would like to make sure we have a smooth implementation and minimize end-consumer/merchant impact. Thanks!
This question was
closed
by
clover-community-bot for the following reason: automated
All new apps on the clover platform have a limit of 50 requests/second. If the app needs to make more requests than that you can reach out and get that limit increased.
For existing apps, a limit is already in place. We've tried to make it large enough that it should not have any impact on your existing use case. We hope to be able to use the ability to lower this limit as a alternative to a complete shutdown when an app is causing performance problems on our api. If Clover returns a 429 status code, your app should halt all requests and use exponential back-off to determine when to try again (wait 1 second, if that fails 2 seconds, then 4, 8... etc).