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: Commvault
providerId: commvault
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Rate Limiting
  - Backup
  - Data Protection
description: Commvault Cloud REST APIs are bundled with each subscription. Commvault publishes API references
  (api.commvault.com / documentation.commvault.com) but does not publish a single per-tier numeric rate-limit
  table; throttling defaults are tied to the customer's CommServe / Cloud tenant capacity. Self-managed
  software customers govern throughput at the CommServe level.
sources:
  - https://documentation.commvault.com/
  - https://api.commvault.com/
notes: No published per-second numeric ceiling; effective throughput is bounded by tenant size and CommServe
  capacity.
responseCodes:
  throttled: 429
limits:
  - name: Commvault Cloud REST API
    scope: tenant
    metric: varies
    limit: see Commvault documentation; bounded by tenant capacity
policies:
  - name: Backoff
    description: Use exponential backoff with jitter on 429/503 responses; honor Retry-After when returned.
  - name: Tenant-bounded
    description: Effective throughput is bounded by the customer's CommServe / Cloud tenant resources
      rather than a public per-second ceiling.
  - name: Token-based auth
    description: Authentication tokens have a finite lifetime; clients must refresh tokens, which is rate-limited
      per account.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com