Adobe · Rate Limits

Adobe Rate Limits

Rate limits across the Adobe API surface are service-specific. Document Services and Firefly publish per-API-key request quotas; Experience Platform uses sandbox-scoped throttling; Acrobat Sign limits are documented per endpoint. This artifact captures the umbrella policy; consult per-service rate-limit pages for numeric ceilings.

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

It captures 2 rate-limit definitions, measuring varies.

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

Tagged areas include Rate Limiting, Analytics, Creative Cloud, Document Services, and Experience Cloud.

2 Limits Throttle: 429 Quota: 429
Rate LimitingAnalyticsCreative CloudDocument ServicesExperience CloudGenerative AIPDF

Limits

Per-service quotas (varies) api-key
varies
see service-specific limits documentation
Each Adobe API documents its own per-second / per-minute ceilings; consult the developer.adobe.com docs for the specific service.
Generative-credit pacing (Firefly) account
varies
see https://developer.adobe.com/firefly-services/docs/
Firefly throttling is governed by the generative credit balance and the per-minute concurrent-request ceiling specific to each Firefly endpoint.

Policies

Backoff Strategy
Implement exponential backoff with jitter and honor any Retry-After header.
Per-service throttling
Limits are enforced per-API and per-API-key; exceeding one service does not impact unrelated services on the same Adobe IMS organisation.
Enterprise raise
Enterprise customers can negotiate raised quotas for production traffic via their Adobe account team or technical account manager.

Sources