Salesforce Service Cloud APIs · Rate Limits

Service Cloud Rate Limits

Salesforce meters the platform API by a rolling 24-hour REQUEST ALLOCATION per ORG, computed from the org's edition and its purchased licences — not by a per-key requests-per-second rate. There is no burst window and no per-endpoint limit. The runtime signal is the Sforce-Limit-Info response header, returned on every REST call.

Service Cloud Rate Limits is the machine-readable rate-limit profile for Salesforce Service Cloud APIs on the APIs.io network, in the API Commons Rate Limits shape.

It captures 6 rate-limit definitions, across the Developer Edition, Enterprise / Professional (with API access), Unlimited / Performance, Full Sandbox, and Developer Edition and Trial orgs tiers, measuring requests and concurrent_requests.

Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 403.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, quotaExceededCode, queryTimeout, queryTimeoutCode, soapTimeoutCode, and note.

Tagged areas include Cloud, CRM, Customer Service, Enterprise, and Salesforce.

6 Limits Exhausted: HTTP 403 Quota: 403 limitremainingresetretryAfter
Transcribed from the provider's documentation on 2026-08-27 — developer.salesforce.com/docs/atlas.en-us.salesforce_app_....
View Source
CloudCRMCustomer ServiceEnterpriseSalesforceSupport

Limits

Total API requests per 24 hours org
requests · 24h
15000
Total API requests per 24 hours org
requests · 24h
Total API requests per 24 hours org
requests · 24h
Total API requests per 24 hours org
requests · 24h
5000000
Concurrent long-running requests (20+ seconds) org
concurrent_requests
5
Concurrent long-running requests (20+ seconds) org
concurrent_requests
25

Policies

Read the header, not the docs
Sforce-Limit-Info comes back on every REST response. An agent should parse it before every write burst rather than modelling the org's allocation from the edition.
No Retry-After
Because Salesforce publishes no Retry-After, a client that hits REQUEST_LIMIT_EXCEEDED must wait out the rolling 24-hour window rather than back off for a stated interval. Treat it as a hard stop, not a throttle.
Concurrency is separate from volume
The 20-second concurrent-request ceiling is enforced independently of the daily allocation. Long SOQL against a large Case table is what usually trips it.
Move bulk work off the sync API
Bulk API 2.0 jobs are metered differently from synchronous REST calls; large Case or Knowledge migrations belong there.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/service-cloud-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.