Learn About Daily Rate Limits

In the multitenant Salesforce architecture, orgs share a set of pooled resources. To assure consistent performance for everyone, we allocate a certain amount of usage for certain types of actions per 24-hour period. We want to keep the flow of traffic moving and avoid bottlenecks.

We aggregate this load across each instance in a few different ways.

Allocations Based on Licenses
The more licenses you purchase, the higher your allocations of certain features or functions. Maximum daily SOAP and REST API calls and platform event delivery allocations are examples of this. 

To understand what happens as you approach a 24-hour limit, let’s look at an example.

Platform event limits apply to a 24-hour cycle. Before delivering new events, such as a change in order status, to subscribed clients, Salesforce checks your allocation and how many events have been used in your Salesforce org in the last 24 hours. If the number of events used is lower than the 24-hour allocation, Salesforce delivers events to subscribers. If you did hit your allocation for events in the previous 24 hours, Salesforce doesn’t deliver new events. But, they’re queued within a brief time window until event allocation is available.

As you trigger each new event, Salesforce checks your allocation against the number of events in the previous 24 hours. This period “rolls” with each new event—it doesn’t reset at a specific time. It’s always 24 hours from the new event trigger. And again, if you haven’t used your allocation in the previous 24 hours, the event is delivered to subscribers.

Don’t wait for the system to tell you that you have run out of allocations. Be proactive. Look at your usage and determine if you should continue to trigger events or make API calls or requests.

You can do this either declaratively or programmatically. If you monitor your rate limits declaratively, you need to stop any integrations manually, which is not the most ideal scenario. If you do it programmatically, your apps might be able to self-monitor to avoid the limits.

  

 

 

Also, API Usage Notification sends emails when you use a defined percentage of your allocation.

 

And, the Salesforce Shield add-on includes more detailed event monitoring, including your historical usage rates.

Programmatic Monitoring Options

Use the following to monitor both events and API usage programmatically.

HTTP/1.1 200 OK
Date: Mon, 20 May 2013 22:21:46 GMT
Sforce-Limit-Info: api-usage=110018/100000
Last-Modified: Mon, 20 May 2013 20:49:32 GMT
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
{
...
}      

<?xml version="1.0" encoding="UTF-8"?>
...
<soapenv:Header>
 <LimitInfoHeader>
   <limitInfo>
     <current>5</current>
     <limit>5000</limit>
     <type>API REQUESTS</type>
   </limitInfo>
 </LimitInfoHeader>
...
</soapenv:Body>
    </soapenv:Envelope>

{
"ConcurrentAsyncGetReportInstances" : {
"Max" : 200,
"Remaining" : 200
},
"ConcurrentSyncReportRuns" : {
"Max" : 20,
"Remaining" : 20
},
"DailyApiRequests" : {
"Max" : 100000,
"Remaining" : 14998
},
"DailyAsyncApexExecutions" : {
"Max" : 250000,
"Remaining" : 250000
},
...
"HourlySyncReportRuns" : {
"Max" : 500,
"Remaining" : 500
},
"HourlyTimeBasedWorkflow" : {
"Max" : 50,
"Remaining" : 50
},
"MassEmail" : {
"Max" : 10,
"Remaining" : 10
},
"SingleEmail" : {
"Max" : 15,
"Remaining" : 15
},
"StreamingApiConcurrentClients" : {
"Max" : 20,
"Remaining" : 20
}
}      

You’re monitoring and paying attention to your usage. That’s great. What do you do when you see those numbers approaching your allocation? It’s time to be a gatekeeper. You have several options.

• You can program your app to call the REST limits resource periodically, to see where you are against the limit, and then decide whether to make the subsequent call.
• You can manage the API-enabled profiles, disabling access to the Salesforce API for those user profiles that absolutely do not need access to it. You can do this with a single user perm: API Enabled.
• You can set objects as Light vs. Enterprise. For those objects that should have only limited API interaction, you can set objects as Light, so that you cannot use the Streaming or Bulk API against them. For more information, see Store Information That’s Unique to Your Organization.
• Restrict API access only to approved apps. For those times when you only want certain apps to use the API, you can use the API client to allowlist the feature to restrict which apps actually can use the API. You also can restrict usage of the approved apps to only approved users using OAuth policies, further restricting access. See Manage API Access.

Evaluate your needs. Remember, these are allocations. It can be time to right-size your org and upgrade your edition or add-ons.

1. From Setup, enter Profiles in the Quick Find box and select Profiles.
2. Clone the Standard User profile with the following settings: Use existing profile: Standard User Profile Name: No API Access
3. Click Save.
4. Click Edit on the No API Access page.
5. Under Administrative Permissions, deselect API Enabled. Don’t see Administrative Permissions on the profile page? Dont worry. Salesforce displays profile permissions based on your org settings. If you’re using the Enhanced Profile User Interface, search for API Enabled on the No API Access profile page, or find API Enabled under System Permissions. Then, deselect it.
6. Click Save. Now you can assign the Standard User profile to users who need apps that use the API, such as Data Loader, and assign the No API Access profile to data entry users who don’t need API access.