Hi @ajithr,
Since you have said that you want to build this as a Freshworks app, there are a few ways to implement this:
-
If you do not need historical data: If you are building a Freshworks App, you can listen to
onTicketCreateproduct event to get details of tickets as they are created. This way, you will not need to call the REST API for tickets that are created after the app is installed. You can choose to cache theonTicketCreateevent data in the app’s data store and use a scheduled function to periodically send batches of updates to the remote server. Given that the rate of ticket creation may be high, you are unlikely to hit Request API rate limits if you use batching + scheduled functions. -
If you need historical data: Additionally, if you need historical data, you can still use a scheduled function to call the Freshdesk REST API periodically. To do so, you can use the List all Tickets or Filter Tickets endpoints which allow fetching a list of tickets with an
updated_sinceor withcreated_attimestamps. You can then send those ticket data to the external services using Request Method.
You are unlikely to hit any rate limits if you use either of these implementation scenarios. But if you still do, you can request an increase in rate limits for an app installation (this is tied to a specific app installation in a specific account) using the form to request an increase of Platform rate limits.
For more details on what rate limits can be modified, please see Get assistance in extending platform API limits for your apps.
Finally, the usage of Freshdesk REST APIs is governed by the REST API rate limits which are different from the platform feature rate limits applicable for apps installed in an account. If you need to request changes to REST API rate limits, I believe you will have to upgrade the plan or add more agents. For this, please get in touch with support@freshdesk.com for more details about REST API rate limits.