Adobe Campaign · Rate Limits

Adobe Campaign Rate Limits

Adobe Campaign v8 enforces a throughput ceiling on its API layer, measured in transactions per second. Adobe publishes the existence of the limit, the unit, and the failure status — but not the number. The number is contractual: it is set per customer against the Adobe Campaign Managed Cloud Services product description and the license, and Managed Cloud Services customers can ask Adobe to adapt the throttle per API. Access to the REST surface is itself gated (on-demand, FDA environments only, not available on Enterprise/FFDA deployments).

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

It captures 2 rate-limit definitions, measuring transactions_per_second and varies.

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

Tagged areas include Rate Limiting, Marketing, and Campaign Management.

2 Limits Throttle: 429
Rate LimitingMarketingCampaign Management

Limits

Campaign v8 API layer throughput instance
transactions_per_second
undisclosed
License scale limitations contract
varies
see product description

Policies

Backoff strategy
Exponential backoff with jitter on 429. No Retry-After is documented, so a client must choose its own interval.
Per-API throttling
Adobe states the throttle can be adapted "for each API", implying the ceiling is per-endpoint-family rather than one global bucket.
Server-to-server only
Campaign APIs are documented as server-to-server only, so client-side traffic amplification is out of scope by policy.
Access gate
REST API access is on-demand for FDA environments and unavailable on Enterprise (FFDA) deployments — the first limit an integrator meets is entitlement, not throughput.

Sources