Community Hours: Implementation strategies to handle rate-limits

Community Hours - Social Post 1200X628_with CTA

Topic: Build within constraints: Implementation strategies to handle rate-limits

Join the hands-on session on how developers can design Freshworks apps to be performant and stay within the rate-limits. We will study some common use cases we have learnt from our developer community and look at patterns to implement them using available platform features. We will also discuss scenarios where building a middleware (external proxy systems) is a better solution.

The implementations will be based on Platform v2.3 (FDK 9).


  • Rate-limits applicable to Freshworks apps
  • Use case 1: Sending frequent updates to an external API
  • Use case 2: Synchronizing data with an external system
  • Use case 3: Reading data frequently from external data stores
  • Use case 4: Working with APIs that take too long to respond or have a large payload.
  • Common implementation patterns based on these use cases


Kaustav Das Modak, Lead Developer Advocate at Freshworks (Follow Kaustav)



23rd February 2023
5:30 pm IST (India)| 1:00 pm CET| 12:00 pm GMT (London)
Check your time zone

What’s in it for you!

Apps on the Freshworks Developer Platform have to work within the constraints of the rate-limits and timeouts. In our discussions with the developer community, we have discovered some implementation strategies for recurring use cases that developers implement to reduce the rate of resource consumption of their apps.

This session is for you if you expect your apps to encounter rate limits in production and you want to know how you can redesign the implementation to breach rate limits less frequently.


Q1: Why does the custom app get 429 if it sends more than 50 requests/min even if the REST API’s rate-limit has not been breached?
A1: Freshworks REST APIs have an account-specific rate-limit. By contrast, rate limits for platform features, like Request Method, are applicable per app installation. In this scenario, the response with status 429 indicates that the app has breached the Request Method rate limit of 50 rpm.

Q2. There are sublimits with Freshdesk’s REST API (e.g., Ticket Create, Ticket List). However, it does not cover every endpoint support. Is there a way to identify sublimit any particluar endpoint falls under?
A2: Rate limits for Freshdesk REST APIs are based on the plan of the account. The sub-limits apply only to the specific endpoints mentioned in the Rate Limits section of Freshdesk REST API docs. One way to identify the limits applicable to any endpoint is to check the X-Ratelimit-Total and X-Ratelimit-Remaining response headers.

Q3. If apps that use different API keys to make requests to the REST API still share the same overall rate limits for that account, is there a way for us to track the total amount of requests being made across all the installed applications in specific time period?
A3: This can be a feature request! There is no dashboard or report available today. The only way is to look at the response headers like X-Ratelimit-Remaining for each request to find out how many requests are available in the current rate limit window

You can also have your question ready beforehand, as we have a live Q&A during the session, where our fantastic DevExperts will answer your questions.

Can’t attend live? You should still register. We’ll share the recording after the session.
We are looking forward to seeing you at the next event!

1 Like

Did you register for the Community Hours session yet?

Topic: Build within constraints: Implementation strategies to handle rate-limits

We’ll see you tomorrow for a hands-on session on how you can handle the app rate limits and timeouts.

23rd February 2023
5:30 pm IST (India)| 1:00 pm CET| 12:00 pm GMT (London)
Check your time zone