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, in the API Commons Rate Limits shape.

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

Limit state is signalled in the rate_limit_headers, retry_after, and note response headers, and an exhausted limit returns HTTP 429.

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 Exhausted: HTTP 429 rate_limit_headersretry_afternote
Transcribed from the provider's documentation on 2026-08-13 — experienceleague.adobe.com/en/docs/campaign/campaign-v8/d....
View Source
Rate LimitingMarketingCampaign Management

Limits

Campaign v8 API layer throughput instance
transactions_per_second · per 1s
undisclosed/1s
License scale limitations contract
varies
see product description
Adobe's API getting-started page instructs callers to check the scale limitations of their license agreement before performing API calls, and points at the Adobe Campaign Managed Cloud Services 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

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/adobe-campaign-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.