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: Acceldata
providerId: acceldata
created: '2026-05-04'
modified: '2026-08-29'
generated: '2026-08-29'
method: searched
source: https://docs.acceldata.io/api/introduction
docs: https://docs.acceldata.io/api/introduction
note: >-
  REPLACES a 2026-05-04 API-Evangelist-authored scaffold that invented a 10 requests/minute
  free-tier limit and a full set of X-RateLimit-* response headers. Acceldata publishes
  NEITHER. An honest zero is the finding.
tags:
  - Data Observability
  - Rate Limiting
  - Quotas
  - Throttling
description: >-
  Published rate-limit posture for the Acceldata ADOC APIs. Acceldata documents that 429 is
  returned when limits are exceeded but publishes no numeric limit, no window, no scope and
  no rate-limit response headers.
limit_count: 0
limits: []
headers:
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
  published: false
  note: >-
    No RateLimit-*, X-RateLimit-* or Retry-After header is documented anywhere, and none is
    declared on any of the 140 published operations. An agent has no runtime signal — it can
    only discover a limit by hitting it.
responseCodes:
  throttled: 429
  documented_as: >-
    "429 Too Many Requests — The server cannot handle the current level of concurrent API
    calls. This happens when rate limits are exceeded."
  source: https://docs.acceldata.io/api/introduction
  declared_on_operations: 0
  note: >-
    429 appears in the API introduction's status-code table but is declared on ZERO of the
    140 published operations, so a generated client will not model it.
  serviceUnavailable: 503
  gatewayTimeout: 504
  requestTimeout: 408
concurrency_controls:
  - surface: policy execution
    mechanism: 422 single-flight
    detail: >-
      "Previous execution of rule '{name}' has not completed. Not running the rule." —
      returned by triggerDataQualityExecution and triggerReconciliationExecution. This is
      the ONLY published throttling behaviour with concrete semantics, and it is per-rule
      concurrency control rather than a rate limit.
    operations:
      - triggerDataQualityExecution
      - triggerDataQualityExecutionByName
      - triggerReconciliationExecution
      - triggerReconciliationExecutionByName
guidance_published:
  - quote: 'Always test with smaller datasets or sample rows before running bulk operations.'
    source: https://docs.acceldata.io/api/introduction
  - quote: 'Use pagination (limit, offset) to avoid retrieving very large results in one request.'
    source: https://docs.acceldata.io/api/introduction
tenancy_note: >-
  ADOC is deployed per customer against the customer's own control-plane host, so any
  effective limit is a property of that deployment rather than of a shared public gateway.
  That plausibly explains the absence, but it does not substitute for a published number.
summary:
  published_limits: 0
  published_headers: 0
  status_code_on_exhaustion: 429