To avoid the rate limit issues we are using webhooks to retreive orders. However, we can't seem to retrieve order details (item, count, category, modifiers, note, custom info). Is there a method to do this outside of an api call?
No, there is not. The webhook tells you that something has changed, but you need to obtain the details. If you want to reduce API calls you can queue up the ids and make a call every N seconds with just the ids that have changed - https://docs.clover.com/docs/using-filters-to-retrieve-multiple-results-from-an-endpoint.
Always appreciate your help and feedback... Unfortunately, we only had 1 point to share :)
One follow up question:
if we send multiple Ids in filter parameter, would it effect our API usage limit . Let's say we send 10 Ids, in filter parameter to retrieve details of 10 orders. Will it be consider 1 API call or 10 API calls?
"Clover recommends retrieving no more than 100 items per query to avoid hitting limits and performance issues". What does "hitting limits" mean? Are there other limits that exist?
In essence the thought is that if we are retrieving 100 items per query, at some point there will be a max amount of clients that can be supported. 50 api calls per second with 100 items each, that's 5,000 items per second max. Once you have X amount of clients retrieving 5,000 items per second, you will probably hit a limit of 50,000 items per second. Anything beyond that would probably upset the merchant that they have to wait beyond 10 seconds for an order to display.
If there is a possible work around, would love to have your advice.
I am not sure what the hard limit is (I would have to check), I am guessing it is around 1000 and that may work fine. But, on our end we are doing an IN and the statement ends up being very long and at some point I am guessing there could be problems. Yes, you can run into rate limit issues and when you do you can contact developer relations. If you are using the API correctly and efficiently and just have a lot of installs we can bump the limits.
"If you are using the API correctly and efficiently and just have a lot of installs we can bump the limits."
You should advertise this somewhere, like here: https://docs.clover.com/docs/api-usage-rate-limits
sorry I meant 50,000 items in 10 seconds. With each request pulling 5,000 items.
Welcome to the
Clover Developer Community
2 People are following this question.
