As a heavy user of the REST APIs to aggregate and disseminate information across multiple systems, I would like to have a batch API endpoint for updating Features in order to avoid Throttling limitations in the existing one-update-at-a-time REST in API v1.
Background:
Like many organizations, there are many tools that my team interacts with on a regular basis. From these tools we aggregate and analyze information. Post analysis, we want to return a sub-set of the analysis back to the core systems where people are working. The availability of API endpoints makes this possible. Instead of asking for cycle time Monte Carlo simulattors, I can do that myself and post the results. Unfortunately, with a moderate number of teams and cards in Aha, I am hitting throttling limits. The solution is a batch update process. This will make my code and the Aha endpoints more efficient.
Thank you for your idea. We will continue to watch customer feedback here. Though at this time due to other priorities and overall customer demand, we are unlikely to implement this idea. We hope you can understand.
Hi Sandeep,
This idea is set to unlikely to implement due to other priorities and overall customer demand.
However, a workaround could be to write code that looks at the rate limit header and throttles itself when it's making too many requests in a given period of time.
Hope that helps!
Hi,
Is this feature for batch APIs available now?
Regards,
Sandeep