Key changes in metering API Limits

Hello everyone,

We are going to implement a couple of important changes concerning v2.0 API Limits in Zoho CRM, which will be effective from 15 October, 2018. These upgrades guarantee several benefits to the users, such as an increase in the overall API limits, and the removal of time constraints for the API calls.

The two major changes that will be implemented are:

A new system of calculating the API Rate Limits -

Currently, the per minute API rate limits are calculated based on the number of API calls made for a user/min/oauth2 app.

For example, currently in the Enterprise Edition, the API Rate limit is - 100 requests/minute/user/app

However, from now on, instead of calculating the number of API calls made in a minute, the rate limit will be calculated based on the number of concurrent calls made per user per app. Therefore, the rate limits, or the 'concurrency limits' as it shall be termed henceforth, will now specify the maximum number of API calls that can be simultaneously active at a given point of time, for a user per app.

NEW CONCURRENCY LIMITS FOR VARIOUS EDITIONS OF ZOHO CRM -

EDITION	CONCURRENCY LIMITS FOR A USER/APP
Free	5
Standard	10
Professional	15
Enterprise/Zoho One/CRM Plus	20
Ultimate	25

Benefits:

Calculating the API rate limits based on concurrent calls will be hugely beneficial to you, as it prevents all time-based restrictions. For instance, currently in the Enterprise Edition, you can make only 100 calls per minute per app. If you exhaust this rate limit, you will have to wait for the minute to get over, to make the next API call.

However, from now on, with the rate limits being based on the number of simultaneous active calls, rather than on the number of calls made in a minute, there would be no per minute call limit restrictions. You will be able to make any number of API calls in a minute without restrictions, enabling you to work uninterrupted, provided the number of concurrent calls are within the specified limits.

2. An increase in API Limits -

We are also increasing the maximum API call limits that can be made in a 24-hour window. This increase is the result of associating API calls with 'Credits'. These credits will be deducted from your Credit Count, based on the type of the API call that you make. Since the new credit count that we provide is almost double the old maximum API call limits, there will be a huge performance boost.

However, the credit deduction is based upon the intensiveness of the performance, and the memory usage of the operations involved in the API calls. Therefore, although the call limits increase substantially for the commonly used API calls, you will find that they are restricted for the memory-intensive API calls.

The revised Maximum Credit Limits in a 24-hour window are as follows -

EDITION	OLD MAXIMUM CALL LIMITS	NEW MAXIMUM CREDITS
Professional	100,000	200,000
Enterprise/Zoho One/CRM Plus	300,000	500,000
Ultimate	500,000	1,000,000

The credit deduction for some of the API operations are listed below -

API CALLS	CREDITS
Get Users/Roles/Profiles	1
Get list of Modules	1
Get Field Meta Data	1
Get Module Meta Data	1
Get IDs of deleted records	2
Get records with cvid parameter	3
Convert Lead	5
Add/Remove Tags to Multiple records	1 credit for every 50 records
Insert/Update/Upsert	1 credit for every 10 records
Bulk Read Initialize	50
All other APIs	1

As you can see, a commonly used API call, such as Get records, will consume only a minimum amount of credits. However, an intensive API call, such as Convert Lead, will consume more credits, because of the heavy amount of operations involved in it.

Note: The Insert/Update/Upsert API call can be made for a maximum of 100 records, and the Add/Remove Tags to Multiple records API call can be made for a maximum of 500 records. Therefore, the maximum number of credits that can be deducted for these two API calls are 10.

How will these changes affect me?

These changes will not affect the functioning of your existing CRM system. You can carry on working with your CRM in the usual manner. These changes are only concerning the way we meter the API limits. Since we are implementing an entirely different method of calculating the API limits, you will find an increase in your overall limits for the most part, and a decrease in the limits for certain memory-intensive operations alone.

What do I have to do on my part?

You can rest assured that there is absolutely no action required to be taken on your end. You need not modify or make any changes to your CRM.

If you have any further queries regarding these changes, you can contact our customer support or write to us at: support@zohocrm.com.

Update 1 -

As of 25 October 2018, the credit system has been enabled for all Zoho CRM users. However, the concurrency limits are being implemented to Zoho CRM users in phases. If the concurrency limits have not yet been enabled for your CRM, the old API Rate Limits will still be active, until the activation of concurrency limits.

You can find out whether concurrency limits have been activated for you or not, by the response headers that are returned for your HTTP requests. If these response headers- X-RATELIMIT-LIMIT, X-RATELIMIT-REMAINING, X-RATELIMIT-RESET are returned for your requests, then the concurrency limits have not been activated for you yet, and your API limits are still restricted on a per-minute basis.

The API Rate limits restricted on a per-minute basis are as follows -

Zoho CRM Edition	API Rate Limits
Free Edition	50 requests/minute/user/app
Standard Edition	100 requests/minute/user/app
Professional Edition	100 requests/minute/user/app
Enterprise Edition	100 requests/minute/user/app
CRM Plus Edition	100 requests/minute/user/app

New to Zoho CRM Plus?

Deliver unforgettable customer experiences

ACCESS ZOHO CRM PLUS

New to Zoho CRM Plus?

Deliver unforgettable customer experiences

ACCESS ZOHO CRM PLUS

New to Zoho Marketing Plus?

Everything you need to run your marketing

ACCESS ZOHO MARKETING PLUS

New to Zoho Marketing Plus?

Everything you need to run your marketing

ACCESS ZOHO MARKETING PLUS

Tout forum

France ZUGs

Zoho SalesIQ Resources

Sticky Posts
Extension pointers: Handle cases with personalized solutions using custom actions
In our last post, we detailed the steps involved in creating a custom action and the workflow from the developer and end user's side. Now let's look at a working example of how we can create a custom action and implement it in a Zoho CRM account to make
Extension pointers - Simple yet significant pointers #13: On change of field value for CRM variables
CRM variables provide global access to a variable across an entire extension. They also help in the storage of user-specific data provided by the user at the time of installation, which can later be fetched to perform data functionalities. Additionally,
Extension pointers: Extend end-user benefits and allow personalization by implementing extensions with custom actions
From our earlier post on custom actions, we know that we can create templated actions, share them with end users, and allow them to reuse those actions to achieve personalized outcomes. In this post, we'll look at how custom actions make it easy for users
Extension pointers - Simple yet significant pointers #12: Functions for Zoho CRM extensions
Functions are essential in achieving logical functionality for an extension. You can easily code your functions in Deluge using drag-and-drop tools to meet your requirements. How to create functions for Zoho CRM extensions in Sigma Go to Sigma and select
Extension pointers - Simple yet significant pointers #11: Testing an extension in sandbox
After developing an extension using the Zoho developer platform, developers will want to test it before publishing it and making it available to end-users/customers. The Zoho developer platform includes a sandbox testing environment, which is a simulated