Kylas API rate Limit

Kylas API rate Limit

Kylas API Rate Limit :-


Rate limiting is applied to control the number of API requests a user can make within a defined period. Requests exceeding these limits will receive a 429 Too Many Requests response. 

The rate limits for each user type are as follows: 



Type
Rate limit
Web / Mobile User
10 requests per second
API Key
5 request per second
Marketplace Apps
10 requests  per second


User Type Descriptions :-

1. Web / Mobile User :

Web Users or Mobile App interact with the Sales CRM platform through the UI interface. API requests made are subject to the rate limit of 10 requests per second. 

2. API Key :

User access platform programmatically using an API key. This API key have a rate limit of 5 requests per second to balance usage across the system. 

3. Marketplace Apps :

Marketplace App Users utilize the platform via integrations with marketplace applications. These Marketplace apps have the highest rate limit of 10 requests per second to accommodate high-volume interactions. 

 

Rate Limit Enforcement :

  • Response Code: When a user exceeds their rate limit, the API responds with 429 Too Many Requests. 

  • Headers Provided: The following headers are included to help users monitor their rate limit status: 

  • X-RateLimit-Replenish-Rate: The number of tokens added per second (e.g., 10). 

  • X-RateLimit-Burst-Capacity: The maximum number of requests that can be made in a short burst (e.g., 20). 

  • X-RateLimit-Remaining: The number of requests remaining in the current window (e.g., 19). 

  • X-RateLimit-Requested-Tokens: The number of tokens consumed by the current request (e.g., 1). 

  • X-RateLimit-Retry-After: The time (in seconds) after which a request can be retried (e.g., 1). 

  • Real-time Monitoring: Users can monitor their API usage via the dashboard provided in their account settings. 

 

Best Practices for Users :

  1. Batch Requests: Optimize your API usage by batching requests wherever possible. 

  1. Respect Limits: Design your applications to respect the rate limits for your user type. 

  1. Exponential Backoff: Implement retry logic with exponential backoff to handle 429 Too Many Requests responses gracefully. 

 


    • Related Articles

    • How to integrate Kylas CRM with your Indiamart account to capture leads?

      This article covers the steps for integrating your Indiamart account with Kylas CRM to automatically fetch leads generated in Indiamart and store them in your Kylas CRM account. Prerequisites Permissions:  Any user with access to the Kylas account ...

    • How to integrate My Operator with Kylas?

      This article covers the steps that need to be performed in order to integrate My Operator with Kylas CRM. Prerequisites Permissions:  Any user with access to the Kylas account API key Product Plans: Explore & Elevate Activities to be ...

    • How to connect Exotel with Kylas CRM?

      This article will help you walkthrough with the steps on how to sync Exotel with Kylas CRM. Prerequisites Permissions - Any user with access to the Kylas account API key or having access to Kylas marketplace. (a) Contact - read, read all, create, ...

    • How to connect Kylas with My Operator?

      This article covers the steps that need to be performed in order to integrate My Operator with Kylas CRM. Prerequisites Permissions: Any user with access to the Kylas account API key. a) Contact - read, read all, create, update, call (b) Company - ...

    • How to integrate Mcube with Kylas?

      This article covers the steps that need to be performed in order to integrate Mcube with Kylas CRM. Prerequisites Permissions:-   For Admin:- Access to the Kylas account API key For Member:- Kylas CRM call permission Product Plans: Elevate Activities ...