What happens when the daily API limit is reached?

Further API calls are rejected until the rolling 24-hour window clears. Integrations fail rather than queue, so the practical effect is a partial outage of anything that talks to the org.

How often are limits recalculated?

API request limits use a rolling 24-hour window. Storage figures update periodically rather than in real time, so a large delete may not show immediately.

Are governor limits the same as org limits?

No. Governor limits apply per transaction (SOQL queries, DML rows, CPU time) and are enforced in Apex. Org limits are allocations across the whole org, such as storage and daily API calls.

How to Check Salesforce Org Limits

Check Salesforce org limits - API calls, data storage, file storage, and daily email - from Setup, the limits API, and the browser, before you hit them.

Updated 2026-09-09

The limits that break an org are rarely the ones anyone was watching. Daily API calls climb quietly as integrations are added, and storage fills a percentage point at a time until an import fails.

Here is where each number lives, and which ones to check on a schedule rather than after an incident.

Where the numbers live in Setup

Setup → Company Information: data storage, file storage, and licence counts.
Setup → System Overview: a dashboard of the limits most likely to bite, including API usage.
Setup → API Usage Notifications: alerts when API consumption crosses a threshold.

The limits worth watching weekly

Daily API requests - the first thing an integration exhausts.
Data storage and file storage as a percentage of the allocation.
Daily workflow emails and single-email limits.
Async Apex and platform event usage in orgs with heavy automation.

Reading limits from the browser

The REST limits endpoint returns every limit and its remaining headroom as JSON. TurboKit surfaces that same data in a panel inside Salesforce, so a limits check is a click rather than a Setup navigation or a hand-built API call.

The underlying REST call

GET /services/data/v61.0/limits

What to do before you hit one

Set API usage notifications at 70% rather than 90% - you need lead time to find the offending integration.
Archive or delete stale records and attachments; file storage is usually easier to reclaim than data storage.
Move chatty integrations to the Bulk API, which consumes far fewer API calls per record.

Frequently asked questions

What happens when the daily API limit is reached?: Further API calls are rejected until the rolling 24-hour window clears. Integrations fail rather than queue, so the practical effect is a partial outage of anything that talks to the org.
How often are limits recalculated?: API request limits use a rolling 24-hour window. Storage figures update periodically rather than in real time, so a large delete may not show immediately.
Are governor limits the same as org limits?: No. Governor limits apply per transaction (SOQL queries, DML rows, CPU time) and are enforced in Apex. Org limits are allocations across the whole org, such as storage and daily API calls.