specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Adobe Campaign
providerId: adobe-campaign
created: '2026-05-04'
generated: '2026-08-13'
method: searched
source: >-
  https://experienceleague.adobe.com/en/docs/campaign/campaign-v8/developer/api
  (fetched 2026-08-13, HTTP 200) and
  https://experienceleague.adobe.com/en/docs/campaign/campaign-v8/developer/apis/get-started-apis
  (HTTP 200). Upgraded from the 2026-05-04 bulk-sweep `generated` artifact:
  the throttle, its unit (TPS), the exhaustion status and the negotiation path
  are now quoted from Adobe's own documentation rather than inferred.
modified: '2026-08-13'
reconciled: true
tags:
  - Rate Limiting
  - Marketing
  - Campaign Management
description: >-
  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).
notes: >-
  The honest shape of this artifact is: limit documented, value withheld. That
  is different from undocumented — an integrator knows a 429 is coming and knows
  who to call, but cannot size a job in advance without asking their Adobe
  representative. Two further gaps matter to an agent: Adobe documents NO
  RateLimit-* or Retry-After response headers, so the only runtime signal is the
  429 status itself; and 429 is not declared in any published Campaign OpenAPI,
  including the ones in openapi/ here, so a spec-driven client will treat it as
  an unmodelled failure.
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limit_count: 1
limits:
  - name: Campaign v8 API layer throughput
    scope: instance
    metric: transactions_per_second
    window: 1s
    limit: undisclosed
    burst: undisclosed
    status_on_exhaustion: 429
    negotiable: true
    quote: >-
      "Adobe Campaign v8 comes with a limit on the throughput (TPS) of our API
      layer. Breaking the limit leads to standard HTTP error (429). As a Managed
      Cloud Services user, you can contact Adobe to adapt the throttling for each
      API."
    source: https://experienceleague.adobe.com/en/docs/campaign/campaign-v8/developer/api
  - name: License scale limitations
    scope: contract
    metric: varies
    limit: see product description
    note: >-
      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.
    source: https://helpx.adobe.com/legal/product-descriptions/adobe-campaign-managed-cloud-services.html
headers:
  rate_limit_headers: []
  retry_after: undocumented
  note: No rate-limit response headers are documented on either the REST or the Classic surface.
policies:
  - name: Backoff strategy
    description: >-
      Exponential backoff with jitter on 429. No Retry-After is documented, so a
      client must choose its own interval.
  - name: Per-API throttling
    description: >-
      Adobe states the throttle can be adapted "for each API", implying the
      ceiling is per-endpoint-family rather than one global bucket.
  - name: Server-to-server only
    description: >-
      Campaign APIs are documented as server-to-server only, so client-side
      traffic amplification is out of scope by policy.
  - name: Access gate
    description: >-
      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:
  - https://experienceleague.adobe.com/en/docs/campaign/campaign-v8/developer/api
  - https://experienceleague.adobe.com/en/docs/campaign/campaign-v8/developer/apis/get-started-apis
  - https://helpx.adobe.com/legal/product-descriptions/adobe-campaign-managed-cloud-services.html
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com