This document outlines the API limits for Freshworks' Sales and Support products. It begins with a list of products and their corresponding modules or objects, followed by a breakdown of API limits based on the plan for each module or object.
Product and Module API Breakdown
The table below outlines the availability of Product and Module API:
Module/Object | Product | ||||||
Freshdesk | Freshdesk Omni | Freshchat | Freshcaller | Freshsales | Freshsales Suite | Freshmarketer | |
Tickets | Yes | Yes | |||||
Chats/Conversations | NA | Yes | Yes | NA | NA | Yes | NA |
CRM Contacts and Accounts | NA | Yes | Yes | Yes | Yes | Yes | Yes |
CRM Deals | NA | NA | NA | NA | Yes | NA | NA |
Marketing Campaigns and Journeys | NA | NA | NA | NA | NA | Yes | NA |
| Phone | NA | Yes | NA | Yes | NA | Yes | NA |
Product and Plan API Breakdown
The following tables outline the API Access limit based on plans:
Chats/Conversations
Ticketing
Contacts, Accounts, and Deals
Marketing Campaigns and Journeys
Phone
Note:
The API limits mentioned in this article do not apply to Freshchat Classic, Freshcaller Classic, Freshsales Classic, and Freshmarketer Classic.
If you want to increase the API limit for any of the modules, drop an email to [email protected]
Certain limits exist to control the number of API requests sent from an account. Below are a few points to be noted regarding the limit:
Limit: The limit is calculated as requests per min/hour per account.
Indicator: If the limit is reached, your response status code reads 429 (Too many requests).
This limit is on an account level for Chat/Conversations only. For other modules, it is at an agent level. It is irrespective of the number of users.
This limit applies to all the activities performed through API requests.