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 Analytics
providerId: adobe-analytics
created: '2026-05-04'
generated: '2026-08-13'
method: searched
modified: '2026-08-13'
reconciled: true
source: https://developer.adobe.com/analytics-apis/docs/2.0/guides/faq/
sources:
  - https://developer.adobe.com/analytics-apis/docs/2.0/guides/faq/
  - https://raw.githubusercontent.com/AdobeDocs/analytics-2.0-apis/main/src/pages/guides/faq.md
tags:
  - Rate Limiting
  - Analytics
  - Web Analytics
description: >-
  Adobe publishes a single hard numeric rate limit for the Adobe Analytics 2.0 APIs in
  the Analytics 2.0 API FAQ: 12 requests every 6 seconds per user (approximately 120
  requests per minute). Exceeding it returns HTTP 429 with an Adobe error envelope
  carrying error_code 429050. Adobe also documents a 60-second request timeout on
  adobe.io. No RateLimit-* / X-RateLimit-* response headers are documented, and none is
  claimed here — an agent gets no runtime budget signal from this API and must treat the
  429 itself as the only feedback.
limit_count: 1
limits:
  - name: Adobe Analytics 2.0 API request rate
    scope: per-user
    window: 6s
    limit: 12
    equivalent: ~120 requests per minute
    burst: null
    applies_to:
      - https://analytics.adobe.io/api/{globalCompanyId}
    quote: >-
      "The enforced rate limit for API calls is 12 requests every 6 seconds per user (or
      approximately 120 requests per minute)."
    source: https://developer.adobe.com/analytics-apis/docs/2.0/guides/faq/
response_on_exhaustion:
  status: 429
  media_type: application/json
  body: '{"error_code":"429050","message":"Too many requests"}'
  quote: >-
    "When you exceed this rate limit, API calls return a 429 HTTP response code with the
    following response body: {"error_code":"429050","message":"Too many requests"}"
headers:
  documented: false
  ratelimit_headers: []
  retry_after: false
  note: >-
    Adobe documents no RateLimit-*, X-RateLimit-* or Retry-After response headers for the
    Analytics 2.0 APIs. Clients cannot read remaining budget or reset time from a response;
    they must implement client-side pacing and back off on 429.
timeouts:
  - name: adobe.io request timeout
    seconds: 60
    quote: 'Requests submitted through adobe.io currently time out at 60 seconds.'
    source: https://developer.adobe.com/analytics-apis/docs/2.0/guides/faq/
undocumented_surfaces:
  - name: Bulk Data Insertion API
    host: https://analytics-collection.adobe.io/aa/collect/v1
    note: >-
      No numeric request-rate ceiling is published for bulk ingestion; Adobe documents
      per-file format and size constraints instead. Recorded as undocumented rather than
      estimated.
  - name: Livestream API
    host: https://livestream.adobe.net
    note: No published concurrency or connection-rate ceiling.
  - name: Data Repair API
    host: https://analytics.adobe.io/api/{globalCompanyId}/datarepair/v1
    note: >-
      No separate published rate limit; server-call estimate must be run before a repair
      job, which acts as the practical throttle.
policies:
  - name: Adobe best-practice guidance
    description: >-
      Adobe's own guidance in the same FAQ: make multiple smaller requests instead of one
      large request, and request data once then cache it.
    source: https://developer.adobe.com/analytics-apis/docs/2.0/guides/faq/
  - name: Backoff strategy
    description: >-
      No Retry-After is served, so exponential backoff with jitter on 429 is the only
      viable client strategy.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com