We are currently utilizing the Clover Developer API for a simple integration that includes order creation (with line items + modifiers) and payment (via an integration with the Spreedly payment platform).
Due to the API's inability to bulk create line items with modifiers, we have implemented the recommended throttling / back-off as recommended by Miguel Montemayor to respect Clover's 16/token + 50/app limits (per second) across our application.
Despite this, we are still consistently running into 429 "Too Many Requests" responses from the Clover API. Inspecting the headers from some of these responses reveals X-RateLimit-tokenLimit: 5, which based on this link is supposed to be 16 per second, per token.
We are also sometimes seeing this response during testing on some of our first few API calls in a given timeframe where we are almost positive that we should be nowhere near the API rate limit (for example, the 2nd or 3rd call to /orders already throws a rate limit).
- What are the current rate limits (per token, per app) in a production environment?
- Is there a reason why we would trigger these limits before we believe our app should be?
- Is it possible to get any of these limits increased?
