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 Premiere Pro
providerId: adobe-premiere
generated: '2026-08-30'
method: searched
created: '2026-05-04'
modified: '2026-08-30'
source: >-
  Searched the Creative Cloud Libraries documentation tree on developer.adobe.com and read the
  Adobe-published OpenAPI (openapi/adobe-premiere-cc-libraries-api-openapi.json, harvested from
  AdobeDocs/cc-libraries-api-spec) on 2026-08-30.
supersedes: >-
  This file previously carried a bulk-sweep scaffold dated 2026-05-04 that invented per-tier quotas
  and response headers. Adobe publishes neither. The scaffold has been removed rather than left to be
  read as provider-published limits.
limit_count: 0
limits: []
headers: []
status_on_exhaustion: 429
note: >-
  Adobe declares HTTP 429 "Too Many Requests — The user has sent too many requests in a given amount
  of time" on 4 of the 25 operations in its published Creative Cloud Libraries contract, so throttling
  demonstrably exists. What it does NOT publish is any number and any runtime signal: there is no
  documented requests-per-second or per-day figure anywhere in the developer documentation, and the
  spec declares no `Retry-After`, no `X-RateLimit-*` and no `RateLimit-*` response header on any
  operation. A client — and especially an autonomous agent — therefore cannot pace itself against
  this API. It can only retry with blind jittered exponential back-off and treat 429 as the sole
  feedback channel. This is the single largest runtime gap in the surface.
operations_declaring_429:
- postLibraryElements
- updateLibraryElements
- putLibraryElementRepresentations
- postLibraryComponent
soft_limits_documented:
  detail: >-
    The only published numeric bound on this API is a pagination cap, not a rate limit: `limit` on
    GET /api/v1/libraries accepts 1..10 and defaults to 10.
  source: https://developer.adobe.com/creative-cloud-libraries/docs/api/
uxp_surface:
  applicable: false
  note: >-
    The Premiere UXP API runs in-process inside Premiere Pro. There is no network call to throttle;
    the constraint there is the project.lockedAccess() sequencing requirement, not a rate limit.
evidence:
- url: https://raw.githubusercontent.com/AdobeDocs/cc-libraries-api-spec/main/openapi.json
  status: 200
  finding: '429 declared on 4 operations; zero rate-limit response headers declared anywhere.'
- url: https://developer.adobe.com/creative-cloud-libraries/docs/integrate/guides/
  status: 200
  finding: No rate limit, throttling or quota guide in the Integrate section.