We primarily use Oracle API for the financial database to deal with all the financial things.

In our case, it's primarily used for integrating with financial databases and managing all the financial transactions. We've integrated it with REST APIs from banks to enable payments. So, if a payment needs to go through, it gets routed to the relevant vendor via their bank through our Oracle API.

So, the system connects to our Oracle API, which then integrates with third-party bank APIs to handle payments without exposing our ERP database directly.
We use Oracle API as a central hub to connect and manage all these third-party APIs, acting as a barrier between them and our core ERP database. This way, we can handle all the transactions securely and efficiently. That's the main purpose of our Oracle API setup.

We are using this solution in the enterprise for publishing APIs to external client systems and internal systems to receive and process requests. We are using this solution for monitoring and securing all inbound and outbound web-service traffic.

We have roughly 100+ published APIs and around 500,000 daily API invocations.

Given the current market situation in the trade community, we don't have plans to increase our usage for at least one to two years.

We are using the product for the APIs, which we are building in-house. We are exposing it to external or even for internal application to application integrations using this gateway.

We are a multivendor solution provider and this is one of the products that we implement for our clients. We also use it internally.

The main reason we use this solution is to centralize APIs.