About API Gateways

An API gateway is a private endpoint that routes REST API calls to a back-end resource, in this case Oracle Integration. You control which API requests can be processed by the API gateway by publishing (or deploying) specified APIs to the gateway.

What Kind of Traffic Is Handled by an API Gateway

Note:

An API gateway allows you to create nuanced rules for REST calls. However, the process can be complex, time consuming, and error prone. If you don't configure everything exactly as required, users might experience issues accessing Process Automation or Visual Builder. See Adding Request Policies and Response Policies to API Deployment Specifications.

REST API calls from the API gateway's virtual cloud network (VCN) to Oracle Integration are routed through the API gateway. Only those APIs you publish (or deploy) to the API gateway are passed through to Oracle Integration.

However, the API Gateway service doesn't support SaaS event-based APIs, so if you're using SaaS event-based integrations, you must use a custom endpoint instead. See Configure a Custom Endpoint for an Instance.

What Kind of Traffic Isn't Handled by an API Gateway

Non-REST API calls aren't handled by an API gateway.

The following traffic is non-REST API traffic:

• Users working in the Oracle Integration user interface (design-time), including using Process Automation and Visual Builder
• Users working in the Oracle Cloud Infrastructure Console user interface
• SOAP calls

Access for non-REST API traffic is managed with the Oracle Integration instance allowlist. See Configure an Allowlist for Your Instance.