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: ClickHouse
providerId: clickhouse
created: '2026-05-04'
modified: '2026-09-05'
generated: '2026-09-05'
method: searched
source: https://clickhouse.com/docs/cloud/manage/api/api-overview
source_note: >-
  ClickHouse publishes exactly one numeric rate limit, on the Cloud API overview page. This artifact REPLACES
  the 2026-05-04 scaffold, which asserted per-tier request quotas and a full X-RateLimit-* header set that
  ClickHouse does not in fact publish.
description: >-
  Published rate limits for the ClickHouse Cloud control-plane API. The number is published; the runtime
  signal is not.
limit_count: 1
limits:
  - name: Cloud API key request rate
    scope: per-api-key
    api: https://api.clickhouse.cloud/v1
    limit: 10
    metric: requests
    window: 10s
    burst: not documented
    increase: contact support@clickhouse.com for a higher limit
    source: https://clickhouse.com/docs/cloud/manage/api/api-overview
quotas:
  - name: API keys per organization
    scope: per-organization
    limit: 100
    metric: api_keys
    source: https://clickhouse.com/docs/cloud/manage/api/api-overview
headers:
  published: false
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
  note: >-
    No X-RateLimit-*, RateLimit-* or Retry-After response header is documented, and no 429 response is
    declared on any of the 148 operations in openapi/clickhouse-cloud-api-openapi.json. An agent cannot read
    its remaining budget or a recommended backoff from a ClickHouse Cloud API response — it has to count
    locally against the published 10-per-10s figure.
responseCodes:
  throttled: not documented
  quotaExceeded: not documented
database_interface:
  note: >-
    The database interfaces (HTTP :8123/:8443, native TCP, MySQL, PostgreSQL, gRPC) are governed by
    ClickHouse quotas and settings configured per user/service, not by a published platform-wide rate limit.
    The public Playground is documented as having "quotas on its usage" without stating the numbers.
  source: https://clickhouse.com/docs/getting-started/playground