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 Primavera
providerId: oracle-primavera
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Project Management
  - Oracle Cloud
  - Rate Limiting
  - Scheduling
description: >-
  Oracle Primavera REST APIs (P6 EPPM, Gateway, Analytics, Scheduling) do not
  publish per-second or per-minute rate-limit numbers. Throughput on Primavera
  Cloud is bound by the underlying multi-tenant pod capacity; on-premises P6
  EPPM throughput is bound by the customer-deployed application server (Oracle
  WebLogic) and database tier. Bulk operations are typically routed through
  Primavera Gateway with its own batch and pagination patterns.
sources:
  - https://docs.oracle.com/cd/F37125_01/
  - https://docs.oracle.com/cd/F25600_01/
notes: >-
  No public per-tenancy RPS/RPM numbers are published. Set reconciled to true
  after capturing tenancy-specific values from Oracle Support or for
  on-premises deployments after measuring against the deployed WebLogic /
  database capacity.
responseCodes:
  unauthorized: 401
  forbidden: 403
  notFound: 404
  serverError: 500
  serviceUnavailable: 503
limits:
  - name: REST API Throughput (Primavera Cloud)
    scope: tenancy
    metric: varies
    limit: bound by Primavera Cloud pod capacity
    notes: >-
      Throughput is governed by the underlying Primavera Cloud pod and is
      not exposed as a public per-tenancy rate-limit table.
  - name: REST API Throughput (P6 EPPM On-Premises)
    scope: deployment
    metric: varies
    limit: bound by deployed WebLogic / database capacity
    notes: >-
      Throughput is governed by the customer-deployed Oracle WebLogic
      application server and Oracle Database tier hosting P6 EPPM.
  - name: Gateway Batch Job Concurrency
    scope: deployment
    metric: concurrent_jobs
    limit: see Primavera Gateway Administration Guide
    notes: >-
      Concurrent batch synchronization jobs are configured per Primavera
      Gateway deployment.
policies:
  - name: Capacity-Bound Throttling
    description: >-
      Throughput limits are determined by deployment sizing (Primavera Cloud
      pod or on-premises WebLogic / database) rather than a published
      per-tenancy rate-limit table.
  - name: Backoff Strategy
    description: >-
      Clients should implement exponential backoff with jitter on 5xx
      responses; honor any Retry-After header when present.
  - name: Bulk Patterns
    description: >-
      For bulk synchronization with ERP, finance, or BIM systems prefer
      Primavera Gateway adapters over hitting transactional REST endpoints.
  - name: Pagination
    description: >-
      Use the documented pagination parameters on collection endpoints and
      avoid issuing parallel large List operations.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com