CRM API Daily Limit Usage Calculator

Daily API usage is the sum of calls from scheduled jobs, event-driven integrations and everything else, compared with your org’s 24-hour allocation. Enter your own allocation: it depends on edition, licences and purchased add-ons.

Also called: API request budget calculator · Integration API usage calculator

  • Last updated
  • Formula tested against reference values

Your numbers

Example value. Use the 24-hour allocation shown in your org’s limits or system overview page.

For batch syncs: records per run ÷ records per call, plus any lookup calls.

Form fills, order updates or webhooks that each trigger API calls.

Apps, reporting tools and user-driven API traffic.

Result

Share of daily allocation used
—

Calculating…

API calls per day
—
Calls left before the allocation
—
Calls left before the alert threshold
—
Average calls per hour
—
Status
—

How to use this calculator

  1. Enter or choose daily API allocation.
  2. Enter or choose calls per scheduled run.
  3. Enter or choose scheduled runs per day.
  4. Enter or choose events per day.
  5. Enter or choose calls per event.
  6. The share of daily allocation used updates as you type. Use Copy result or Share to keep it.

Method

Calls per day = Calls per run × Runs + Events × Calls per event + Other; Usage = Calls ÷ Allocation × 100; Headroom = Allocation − Calls

Allocation
API calls allowed per 24 hours
Runs
scheduled job runs per day
Events
event-triggered integrations per day

Worked example

  1. Scheduled: 500 × 24 = 12,000 calls.
  2. Event-driven: 20,000 × 2 = 40,000 calls.
  3. Total: 12,000 + 40,000 + 8,000 = 60,000, which is 60% of 100,000.
  4. The 80% alert is at 80,000 calls, so 20,000 calls of headroom remain before it.

These integrations use 60,000 calls a day, 60% of a 100,000-call allocation, leaving 40,000 calls of headroom.

What the result means

Usage above about 80% leaves little room for a bulk re-sync or a traffic spike. The cheapest fixes are usually larger batches (more records per call), bulk interfaces for large loads and event-driven syncs instead of frequent polling.

Assumptions and limits

  • Calls are spread evenly across the day; the hourly average hides peaks.
  • Product names such as Salesforce are trademarks of their owners. This calculator is independent, is not affiliated with or endorsed by any CRM vendor, and uses only the figures you enter.
  • Some platforms measure a rolling 24-hour window and others a calendar day, and some API types do not count towards the allocation. Check your vendor’s rules.
  • Concurrent-request and per-user limits are separate and are not modelled.

Questions

How do I count calls for a batch sync?

Divide the records synced per run by the records each call carries, then add any lookups. 10,000 records at 200 per call is 50 calls per run.

What happens when the allocation is used up?

Depending on the platform, further calls are rejected or throttled until usage falls back under the limit, so integrations fail. Set alerts well below 100%.