Up to 70% off kits30% off services
Salesforce API Limit Calculator
Work out your org's daily API call allocation from your edition and licenses, using Salesforce's published figures. Then add your integrations to see roughly how much of it they use and how much headroom is left for backfills and busy days.
1.Your org
External Identity licenses add 70,000, 750,000 or 4,000,000 calls depending on the pack; check with your Salesforce rep and add them as add-ons.
2.Your integrations
Records per day means records the integration reads or writes each day, not the total in your org. The starter rows are examples; change them to yours.
3.A one-time backfill
| Method | API calls | Days of today's headroom |
|---|---|---|
| One record per call | 250,000 | 2.5 |
| Batched, 200 per call | 1,250 | 0.0 |
| Bulk API 2.0 (25 batches) | 18 | under 1% |
Bulk estimate assumes jobs of about 100,000 records and a few calls each. Bulk batches have their own limit of 15,000 per rolling 24 hours.
Running out of API calls?30% OFF
A $349$499 Salesforce integration health check measures what each integration really uses, finds the waste, and gives you a written fix plan, credited toward the fix.
How the Salesforce API limit is calculated
For Enterprise, Unlimited and Performance Edition (and Professional Edition with API access), Salesforce publishes one formula:
100,000 + (licenses × calls per license type) + purchased add-ons
Calls per license depend on the edition: 1,000 per Salesforce license on Enterprise, 5,000 on Unlimited and Performance. Salesforce's own example: an Enterprise Edition org with 15 Salesforce licenses gets 115,000 calls per 24 hours. Developer Edition has a flat 15,000.
The window is rolling, not a calendar day, and the total is shared by the whole org. Calls made by some Salesforce apps, such as the Salesforce mobile app, don't count; calls from installed managed packages do.
Figures from Salesforce's API request limits and Bulk API limits pages, checked November 2026.
Other limits integrations hit
- Long-running requests. Only 25 requests lasting 20 seconds or more can run at once in production (5 in Developer and trial orgs). Slow queries from several integrations can block each other.
- Timeouts. REST and SOAP calls time out after 10 minutes; queries follow SOQL limits.
- Bulk batches. 15,000 per rolling 24 hours, shared by Bulk API and Bulk API 2.0, and up to 150,000,000 records a day. Bulk API 2.0 query jobs are capped at 10,000 a day.
- When to go bulk. Salesforce suggests Bulk API 2.0 for operations over 2,000 records.
Not sure which integration is the noisy one? Our free Salesforce integration health check covers API usage along with access, matching and error handling.
Frequently asked questions
Salesforce API allocations, Bulk API and what happens at the limit.
Enterprise Edition and Professional Edition with API access get 100,000 calls per 24 hours plus 1,000 for each Salesforce or Salesforce Platform license. Unlimited and Performance Edition get 100,000 plus 5,000 per license. Developer Edition gets 15,000 in total and a Full Sandbox 5,000,000. Other license types add between 0 and 5,000 calls each, and purchased API call add-ons are added on top.
Yes. Salesforce counts REST, SOAP, Bulk API, Bulk API 2.0 and most Connect REST calls toward the same allocation. A Bulk API 2.0 job uses only a handful of calls, though, which is why large loads should use it. Bulk jobs also draw on a separate allowance of 15,000 batches per rolling 24 hours, shared between Bulk API and Bulk API 2.0.
Paid, active orgs can go a little over for short spikes, but Salesforce applies a hard cap and says not to rely on that headroom. Past it, calls fail with REQUEST_LIMIT_EXCEEDED until usage in the rolling 24-hour window drops. Trial orgs, Developer Edition and sandboxes get no overage at all.
Per org. Every integration, connected app and installed managed package draws from the same daily total, which is why one noisy integration can stop all the others.
In Setup, open System Overview for API requests in the last 24 hours, or Company Information for the monthly view. Developers can call the REST /limits resource or read the Sforce-Limit-Info header. You can also set API Usage Notifications to email someone at a chosen percentage.
Sync only records that changed since the last run, batch writes (sObject Collections take up to 200 records per call), use Bulk API 2.0 for anything over about 2,000 records, poll less often or switch to events, and remove connected apps nobody uses. Buying more calls is the last step, not the first.
The allocation uses Salesforce's published figures. The usage side is an estimate from our own rules of thumb: query results in pages of 2,000, batched writes of 200, and a few calls per Bulk API job. Real connectors vary, so compare it with System Overview before making decisions.