Hello @ajmerasunny
I’ve seen your response on the following thread as below: Handling HTTP 429 Error in Connector: Increasing Request Interval?
- “We encountered a similar issue when calling an endpoint to aggregate accounts, and we resolved it by adding a sleep timer to avoid exceeding the rate limit”
Can you please let me know how you’ve handled the account aggregation by introducing the sleep timer in ISC? This is a crucial ask for one of our clients as we’re stuck with the same problem where the client side APIs have rate limits as below and the aggregation task is constantly hitting a 429 error:
- 50 API calls per minute
- 3000 API calls per hour
- 72000 API calls per day
Would like to understand and learn from you on how you’ve handled such a situation during account aggregations. Any inputs from your end would really be appreciated.
Thanks,
Arshad.