Oracle Fusion Cloud Applications · Rate Limits
Oracle Fusion Rate Limits
Oracle Fusion Cloud Applications REST APIs do not publish per-second or per-minute rate-limit numbers in the public REST API guides. Throughput is governed by the underlying Fusion Applications service pod capacity, by per-resource page-size limits, and by Fusion Common's authentication and session controls. Customers experiencing throttling are directed to Oracle Support to raise capacity via a service request, often coupled with a recommendation to switch to bulk-data patterns (FBDI, BI Publisher) for high-volume integrations.
3 Limits
CloudERPHCMOracle CloudRate LimitingSaaS
Limits
REST API Throughput tenancy
bound by Fusion Applications service pod capacity
No public per-tenancy rate is published; throughput is governed by the underlying Fusion Applications pod and may be raised via an Oracle Support service request.
Bulk REST Page Size request
500
Default Fusion REST API page size is 25 rows, configurable up to 500 via the limit query parameter for List operations.
REST Document Upload request
see Fusion REST API guide
Document attachment endpoints enforce per-file size limits documented per resource.
Policies
Backoff Strategy
Clients should implement exponential backoff with jitter on 5xx responses; honor any Retry-After header when present.
Pagination
Use the limit and offset query parameters and follow self/next links rather than issuing parallel large List operations.
Capacity Adjustment
Sustained high-volume integrations should be coordinated through Oracle Support; tenancies on dedicated pods can request capacity increases.
Bulk Data Patterns
For high-volume integrations prefer the BI Publisher bulk extract or File-Based Data Import (FBDI) over hitting transactional REST endpoints.