Skip Navigation

Search

API Throttling and Rate Limiting in Oracle B2C Service
Answer ID 13153   |   Last Review Date 06/29/2026

Does Oracle B2C Service support API rate limiting for inbound API requests?

Environment
Oracle B2C Service
 
Resolution
 

Oracle B2C Service includes mechanisms to regulate inbound API traffic and help maintain service availability. The following sections describe these capabilities and provide links to the relevant documentation.

API Throttling

Oracle B2C Service provides native API Throttling for inbound Public APIs. This feature is designed to regulate concurrent API resource consumption and protect the service from excessive usage.

API Throttling is configured using Managed Applications and Resource Pools. Applications identify themselves using an application code (for example, via the OSvC-CREST-Application-Context header for REST API requests), and Oracle B2C Service allocates database resources according to the configured resource pool.

For more information about API Throttling, see:
API Throttling (REST API documentation)
Regulating Inbound Public API Traffic (Business Administrator Guide)

Customer Portal custom PHP scripts (Connect PHP)

Customer Portal custom PHP scripts use the Connect PHP API to access Oracle B2C Service data.

Oracle B2C Service includes internal server-side protections that help maintain platform stability and protect against abusive script execution and excessive resource consumption. These protections are part of the Oracle-managed cloud infrastructure and are not customer configurable. 

The following documentation provides additional information about Connect PHP and Custom Scripts:
Connect PHP API Developer Guide
Custom Scripts (Customer Portal Developer Guide)

Customer-defined rate limiting

Oracle B2C Service does not provide customer-configurable API rate limiting based on:

  • Requests per day
  • Requests per hour or minute
  • Requests per user or session
  • Requests per source IP address
  • Individual API endpoints


The native API Throttling framework regulates resource consumption per Managed Application, rather than implementing quota-based or endpoint-based rate limiting. If configurable request quotas or rate limiting are required (for example, requests per minute, per IP address, or per user), these controls should be implemented using an external API management solution, reverse proxy, or Web Application Firewall (WAF) positioned in front of Oracle B2C Service.

See also Oracle B2C Service Integration and Extensibility Frameworks Best Practices.