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: Clearstream
providerId: clearstream
created: '2026-05-04'
generated: '2026-09-05'
modified: '2026-09-05'
method: searched
source: >-
  Clearstream API Developer Guide (August 2025), the Clearstream API services page (HTTP 200), and
  the Deutsche Börse Group API Platform consumer documentation —
  https://docs.developer.deutsche-boerse.com/docs/consumer/rate-limiting (HTTP 200, fetched
  2026-09-05). This file replaces a 2026-05-04 bulk-sweep scaffold that invented per-tier limits
  (10/100/1000 rpm and monthly quotas) and X-RateLimit-* headers; Clearstream publishes none of them.
description: >-
  Clearstream publishes no numeric rate limits for its API platform. The group platform it
  publishes into documents the mechanism — a request-count limit and a concurrency (burst) limit
  per time unit, with 429 Too Many Requests on exhaustion — but the actual numbers for any given
  API are shown only inside that API's Detail Page in the Deutsche Börse Digital Business Platform
  catalogue, which requires a registered account. An anonymous read of the catalogue API returned
  401 on 2026-09-05. No rate-limit response headers are named in any published document.
limit_count: 0
limits: []
headers:
  documented: false
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
  note: >-
    No X-RateLimit-*, RateLimit-* or Retry-After header is specified in Clearstream's or the group
    platform's public documentation. An agent cannot read its remaining budget from a response.
responseCodes:
  throttled: 429
  source: https://docs.developer.deutsche-boerse.com/docs/consumer/rate-limiting
mechanism_documented:
  applies_to: APIs published on the Deutsche Börse Group API Platform with rate limiting enabled
  dimensions:
    - name: rate limit
      description: "number of allowed API calls per time unit (the docs' example: 100 calls per second)"
    - name: burst size
      description: "maximum concurrent calls at any time (the docs' example: 50 concurrent calls)"
    - name: time unit
      description: per second, minute, hour or any interval the publisher chooses
  subject: >-
    The docs state the limit description names its subject — per consumer, per end-user, per
    authenticated or unauthenticated session — and warn that publishers may also configure
    undocumented API-level ceilings that apply under very high traffic.
  visibility: API Detail Page → Access & Security section (requires a DBP account)
  evidence:
    - url: https://docs.developer.deutsche-boerse.com/docs/consumer/rate-limiting
      status: 200
    - url: https://developer.deutsche-boerse.com/console/api/v2/apis
      status: 401
      note: Anonymous read of the catalogue API — registration required, so per-API limits are not public.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com