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: Oracle Partitioning
providerId: oracle-partitioning
generated: '2026-08-27'
method: searched
source: openapi/oracle-partitioning-ords-database-api-openapi.json + https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/26.1/orrst/index.html
created: '2026-05-04'
modified: '2026-08-27'
# 2026-08-27: this file previously held a bulk-sweep SCAFFOLD (invented free/professional/enterprise
# limits and invented X-RateLimit-* headers against fake hosts). That scaffold is gone. The honest
# finding is a zero.
description: >-
  Rate-limit posture for the Oracle REST Data Services Database API, the published contract through
  which Oracle Partitioning metadata is read. Oracle publishes NO request quota and NO rate-limit
  response headers for this API, and the contract declares none.
limit_count: 0
headers: {}
headers_declared_in_contract: []
responseCodes: {}
limits: []
finding: >-
  Searched the published contract (352 operations — no 429 response is declared anywhere, and no
  X-RateLimit-*, RateLimit-* or Retry-After header appears in any response) and the ORDS REST API
  documentation. No published limit exists.
why: >-
  ORDS is customer-deployed software, not a vendor-hosted API. There is no Oracle-operated endpoint
  to meter, so throughput is bounded by the operator's own ORDS connection-pool sizing and database
  capacity rather than by a vendor quota. The relevant tuning knobs are ORDS pool settings
  (jdbc.MaxLimit, jdbc.InitialLimit) configured by the operator, not limits published to consumers.
adjacent_controls:
  - name: 'limit query parameter'
    scope: per-request
    note: >-
      Not a rate limit but the only consumption control the contract exposes: 63 operations accept
      limit to cap the page size, and the response echoes the limit the server actually applied.
      The server may reduce the requested limit, which is where an operator ceiling shows up.
  - name: 'Database role requirement'
    scope: per-principal
    note: 'The partitions endpoints require the SQL Administrator or SQL Developer role, which gates access rather than rate.'
  - name: 'OCI Database service limits'
    scope: 'different API'
    note: >-
      The OCI control-plane APIs do publish service limits and throttling. Those apply to the OCI
      Database service, not to this ORDS contract, and are not asserted here.
agent_guidance: >-
  An agent cannot read a runtime rate signal from this API. There is no header to back off on and no
  429 to detect. Treat 503 and connection-level failures as the congestion signal, and use
  exponential backoff with jitter by default.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com