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: PeopleSoft providerId: peoplesoft 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 notes: No vendor-published rate limit numbers. PeopleSoft is typically deployed on customer-controlled Oracle infrastructure (on-prem or OCI), so API throughput is bounded by application server, Integration Broker, and database sizing rather than a vendor-imposed quota. tags: - Rate Limiting - ERP - HCM - Enterprise Software description: PeopleSoft API throughput (REST, Integration Broker, Component Interfaces) is governed by the customer's PeopleTools deployment topology — application server domains, IB queue tuning, and database capacity — not a vendor-side rate limit. sources: - https://docs.oracle.com/en/applications/peoplesoft/index.html responseCodes: throttled: 429 limits: - name: PeopleTools REST / IB scope: deployment metric: varies limit: bounded by customer PeopleTools application server and Integration Broker capacity notes: Rate is determined by domain configuration (PSAPPSRV, PSPUBHND, PSSUBHND), IB queue tuning, and database throughput. policies: - name: Customer-Operated Throttling description: Throttling and retry behavior are managed in the customer's API gateway / Integration Broker configuration, not by the vendor. - name: Backoff description: Standard exponential backoff with jitter is recommended on any 5xx or 429 response. - name: PeopleTools Tuning description: Capacity is tuned via Integration Broker queue partitioning, application server thread counts, and database connection pools. maintainers: - FN: Kin Lane email: kin@apievangelist.com