Salesforce Marketing Cloud · Rate Limits

Salesforce Marketing Cloud Rate Limits

Rate-limit posture for Salesforce Marketing Cloud Engagement, read from Salesforce's own rate-limiting documentation on 2026-08-13. This supersedes the 2026-05-04 bulk-sweep placeholder, which had imported the Salesforce PLATFORM per-edition 24-hour quota model — that model applies to core Salesforce org APIs, not to marketingcloudapis.com, and it is removed here as incorrect. The finding for Marketing Cloud Engagement is the opposite and is itself the story: Salesforce publishes the runtime SIGNAL in full but publishes NO NUMBER. There is no documented requests-per-window figure, no per-endpoint ceiling and no quota surface a client can read before it is throttled. Salesforce says only that "the throttling rate is variable depending on the severity of the impact" and directs customers to their Account Executive.

Salesforce Marketing Cloud Rate Limits is the machine-readable rate-limit profile for Salesforce Marketing Cloud on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include CRM, Email Marketing, Marketing Automation, Marketing Cloud, and Personalization.

3 Limits Throttle: 429 Quota: 429
CRMEmail MarketingMarketing AutomationMarketing CloudPersonalizationRate Limiting

Limits

REST API request throttling account
requests
'If your account is throttled, API requests produce HTTP 429 error messages until the issue is resolved.' No numeric threshold is published.
SOAP API request throttling account
requests
'If API calls from an account negatively impact system performance, Marketing Cloud Engagement temporarily throttles subsequent SOAP API calls from that account. The throttling rate is variable depending on the severity of the impact.' SOAP signals throttling as fault code 17, NOT as an HTTP 429 — a client that only branches on HTTP status will miss SOAP throttling entirely.
MCP server account
requests
Salesforce states 'Marketing Cloud API limits and guidelines apply' to the MCE MCP server. Agent traffic is subject to the same undocumented account throttle as direct API traffic.

Policies

Backoff Strategy
Honour Retry-After on 429 and apply exponential backoff with jitter. Because no quota is published, reactive backoff is the ONLY available strategy — a client cannot precompute a safe send rate.
Token reuse
Cache and reuse the OAuth access token until expiry. Requesting a token per call adds avoidable load against the same account throttle.
Distinguish 50100 from 50200
50100 is a retryable rate limit; 50200 is an account block that retrying will not clear. Treating them the same is the most common client bug against this API.

Sources