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: Zenoss
providerId: zenoss
generated: '2026-08-29'
method: searched
source: https://docs.zenoss.io/api/zenoss-api.html
created: '2026-05-04'
modified: '2026-08-29'
tags:
  - AIOps
  - Monitoring
  - Observability
description: >-
  Zenoss / Virtana Service Observability documents no rate limits. Every /v1 API reference page was
  read — data receiver, event query, event management, model context (entities and maintenance
  windows), dictionary (metrics, entity fields, event fields), actions, credentials and user
  management — and none publishes a quota, a throttle threshold, a burst allowance, a rate-limit
  response header, or a 429 status code. The published status-code tables run 200/400/401/404/409/
  500/501 with no 429 anywhere. The only numeric ceilings Zenoss publishes are on key management
  (200 keys per API Client, 130 Collection Zone keys per user), which are not request limits.
limit_count: 0
limits: []
headers:
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
  note: No rate-limit response header of any kind is documented.
responseCodes:
  throttled: null
  quotaExceeded: null
  note: >-
    429 does not appear in any published status-code table. Whether the platform throttles in
    practice is not observable without a tenant key.
related_ceilings:
  - name: Keys per API Client
    limit: 200
    scope: api-client
    source: https://docs.zenoss.io/admin/clients/zenoss-api.html
  - name: Collection Zone keys per user
    limit: 130
    scope: user
    source: https://docs.zenoss.io/admin/clients/cz-api.html
  - name: Key revocation propagation
    limit: 60 seconds
    scope: api-client
    note: Clients using a deleted key are denied access within 60 seconds — a propagation window, not a rate limit.
    source: https://docs.zenoss.io/admin/clients/zenoss-api.html
evidence:
  - url: https://docs.zenoss.io/api/zenoss-api.html
    status: 200
  - url: https://docs.zenoss.io/api/receiver/data-receiver.html
    status: 200
  - url: https://docs.zenoss.io/api/event-mgmt/event-query.html
    status: 200
history: >-
  This file replaces a 2026-05-04 bulk-sweep scaffold that asserted per-tier X-RateLimit-* headers,
  429 handling and per-minute request limits. None of those were published by Zenoss; they have been
  removed rather than carried forward.