Adobe Campaign · Rate Limits

Adobe Campaign Rate Limits

Adobe Campaign Standard REST API enforces per-tenant throttling. v8/Classic SOAP/REST endpoints are gated by the customer's hosted-instance capacity (typically tied to message-volume contract). Sustained excess returns 429 or 503; bulk and transactional traffic should use staging or transactional endpoints rather than the synchronous REST surface.

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 requests_per_minute and varies.

The profile also includes 3 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 Standard REST API tenant
requests_per_minute
see https://developer.adobe.com/campaign-standard-apis/
Per-tenant throttle on the Campaign Standard REST endpoints; bulk operations should use the staging or batch endpoints.
v8 / Classic SOAP / REST instance
varies
see hosted-instance capacity (contracted message volume)
Throughput is bounded by the customer's hosted-instance capacity rather than a public per-second quota.

Policies

Backoff Strategy
Exponential backoff with jitter; honor Retry-After when present.
Bulk vs synchronous
Bulk staging endpoints decouple ingestion from synchronous API throttling and are the recommended path for high-volume jobs.
Tenant scope
Limits apply across all credentials issued under a single tenant / hosted instance.

Sources