Salesforce API Rate Limits & How to Prevent Hitting Them

Quick answer

Salesforce enforces a 100,000 daily API request limit for Enterprise Edition orgs, plus 1,000 additional requests per user license. The system also caps concurrent long-running requests at 25 (5 for developer orgs) and limits each API call to 10 minutes maximum.

Beyond basic limits, Salesforce restricts Bulk API to 15,000 batches per day with 10,000 records per batch. Report APIs get 1,200 async requests per hour, while Apex callouts max out at 100 per transaction.

Hit these limits? You’ll face blocked requests until usage drops. Coefficient’s managed Salesforce connection bypasses these headaches entirely, giving you real-time CRM data in spreadsheets without quota management or complex retry logic.

Salesforce rate limits

API rate limits

Salesforce uses a sophisticated multi-tier limiting system that catches most integrations off guard:

• Daily request limit: 100,000 base requests per 24 hours (Enterprise Edition) plus 1,000 per user license
• Concurrent requests: Maximum 25 long-running API requests (20+ seconds) in production; 5 in developer orgs
• API timeout: Hard 10-minute maximum per REST or SOAP call
• Bulk API batches: 15,000 batch submissions per day (shared between Bulk API 1.0 and 2.0)
• Streaming API: 50 PushTopics per org, 1,000 subscribers per topic, 200,000 events daily
• Asynchronous requests: 1,200 async requests per hour for specific APIs

API usage limits

Salesforce enforces additional restrictions that compound rate limiting challenges:

• Rolling 24-hour window: Daily quotas measured continuously, not calendar days
• Batch constraints: Maximum 10,000 records per batch, 10MB payload limit
• Report API specifics: 500 synchronous report runs per hour, 20 concurrent sync requests
• Apex callout limits: 100 outbound HTTP requests per transaction maximum
• Debug header restriction: Separate 1,000-call daily limit for debugging-enabled requests
• Per-user OAuth limits: Connect REST API applies hourly limits per user per application

Methods to prevent Salesforce rate limits

• Monitor usage patterns religiously. Track API consumption across all integrations using Salesforce’s usage monitoring tools. Set alerts at 80% capacity to avoid hitting hard limits during peak business hours or month-end reporting cycles.
• Implement smart batching and caching strategies. Use Bulk API for large data operations (respecting the 15,000 daily batch limit) and cache frequently accessed data locally. Optimize SOQL queries to reduce unnecessary API calls and leverage composite requests when possible.
• Use Coefficient for seamless Salesforce integration. Rather than building complex rate limit handling, Coefficient’s Salesforce connector manages all API complexity automatically. You get real-time CRM data without worrying about quotas, timeouts, or error handling.

Step-by-step walkthrough to avoid rate limits using Coefficient

Coefficient eliminates Salesforce API rate limit complexity by handling connections intelligently behind the scenes. You get live CRM data in familiar spreadsheets without managing quotas, implementing retry logic, or monitoring usage patterns.

Setup takes minutes, not weeks:

1. Install Coefficient from Google Workspace Marketplace or Microsoft AppSource
2. Connect Salesforce with secure one-click OAuth (enterprise security built-in)
3. Import any data using visual selectors, SOQL queries, or formula’s 

4. Schedule automatic updates to keep spreadsheets current with Salesforce changes

No quota monitoring needed. No complex error handling. No API expertise required. Coefficient optimizes requests, manages retries, and handles data synchronization automatically while you focus on sales analysis and CRM reporting.

Common use cases that trigger API rate limits

• Sales reporting dashboards with real-time updates. Revenue teams pulling opportunity data, lead scores, and pipeline metrics throughout the day often exhaust the 100,000 daily request limit, especially in high-user orgs.
• Data migration and bulk synchronization projects. Moving historical records or syncing with external systems frequently hits both daily API limits and the 15,000 Bulk API batch restriction simultaneously.
• Multi-app integration environments. When marketing automation, support tools, and business intelligence platforms all access Salesforce concurrently, combined usage often exceeds both daily quotas and concurrent request limits.

Stop fighting API limits

Salesforce rate limiting doesn’t have to derail your CRM workflows. While building custom integrations requires careful quota management and sophisticated error handling, Coefficient provides instant access to live Salesforce data without technical complexity.

Ready to eliminate API rate limit headaches? Get started with Coefficient and connect Salesforce in minutes, not hours.

FAQs

What is the 24-hour API limit in Salesforce?

Salesforce provides 100,000 API requests per 24 hours for Enterprise Edition orgs, plus 1,000 additional requests per user license. For example, an org with 50 users gets 150,000 daily requests. This limit operates on a rolling 24-hour window, not calendar days, and additional requests can be purchased if needed.

What is the rate limit of an API?

API rate limits vary significantly by provider and service tier. Salesforce uses 100,000+ daily requests with concurrent limits, while QuickBooks enforces 500 per minute. HubSpot typically allows 100 requests per 10 seconds, and Google APIs range from 1,000 to 1 million requests per day depending on the service.

What is the bulk API rate limit in Salesforce?

Salesforce Bulk API allows up to 15,000 batch submissions per 24 hours, shared between Bulk API 1.0 and 2.0. Each batch can contain maximum 10,000 records with a 10MB payload limit. These limits are separate from standard API quotas but still count toward overall org usage monitoring.

What is API rate limit 429?

HTTP 429 “Too Many Requests” indicates you’ve exceeded an API’s rate limit. This triggers when you surpass allowed requests per time period (like Salesforce’s daily quota) or concurrent request limits. The response typically includes retry-after headers suggesting when to attempt the request again.