How to handle the API rate lime issue for TFS server

We have built a marketplace app for TFS integration with Freshdesk, which was working fine with TFS server having less number of projects. Recently we encountered customers having more number of projects and there is an API rate limit i.e 50 per minute in TFS .

As a workaround we checked it by adding the manual delay between the API calls and we could able to make all the calls, but since it is a public app the users have to wait to load all projects and it will be more than a minute.

Could you please suggest a way to handle this.

1 Like

Hi @kishore

Can you please help us with the below details?

What is the use case of the app? Describe every flow if it has multiple flows.
How many concurrent users/agents will be using this app?
What is the number of requests made by a single instance of the app, within a given minute?
What is the nature of the API calls being made from the app using $request and can any of them be cached?

Please find below my comments

What is the use case of the app? Describe every flow if it has multiple flows.
Please find the use case in the attached document
Tfs_freshservice_integration.zip (987.3 KB)

How many concurrent users/agents will be using this app?
Since it is a public app we are not sure how many agents will be using this concurrently

What is the number of requests made by a single instance of the app, within a given minute?
Depending on the number of projects we will make the API calls to check whether the project is an Agile project are not

What is the nature of the API calls being made from the app using $request and can any of them be cached?
The API call is to get the project details and it can store in the local DB I believe for future use.

It’s possible to increase the per minute from the Freshworks side if the use-case is valid and this is tied to a specific app installation in a specific account.

For more details, please see Extending platform API limits for your apps

2 Likes

Hi @kishore,

As @ajithr mentioned, for the use case and based on the customer account size, we can increase the rate limit of the app upon request.

Since it’s a public app, if you would like to optimize the solution further to work with the default rate limit, can the first project be loaded first and the rest of the projects be opened a few minutes later with Scheduled Events?