I use the solution in my company as an enterprise application that will be placed in more than 175 places across the world, which would be in different countries. As an API management tool, it will be placed across different regions on Azure Cloud and WSO2's cloud.
We use the solution mainly to protect the frontend and backend proxy APIs. We also use the solution for federating with the identity server. We publish our backend API into WSO2 API Manager and use the proxy API outside. We use the solution for authorization, authentication, and accounting purposes.
We provide this solution to our customers. Most of our clients are enterprise size organizations. We have a partnership with the company and I'm a solutions architect.
Chief Technology Officer at Swifta Systems and Services
Real User
Top 10
2021-09-29T15:48:00Z
Sep 29, 2021
Our normal use case for API Manager is to create pre-configured store users. The administrator who creates those users then sends them their credentials and secure links. We are running API Manager on a Tomcat server. Currently, I am the main person who works with API Manager, because it requires a proper understanding of the APIs.
Vice President at Exzatech Consulting And Services Pvt Ltd.
Reseller
2021-05-26T18:39:00Z
May 26, 2021
We have developed a slew of applications for Bank, that helped transform multiple core banking processes, such as customer onboarding, account servicing, and rapid loan request fulfillment. The solution, which is powered by WSO2’s API management and enterprise integration technologies, seamlessly bridges systems while paving the digital path to a connected financial ecosystem.
Sr. Technology Specialist at a computer software company with 5,001-10,000 employees
Real User
2021-02-10T09:52:46Z
Feb 10, 2021
We're currently evaluating WSO2 API Manager and Kong for development environments and not production environments. We're currently using Apigee and AWS API Database for the production environments.
I work as a software engineer on the WSO2 API management and WSO2 identity and access server, using version 2.6. At my company, Jio India, I have been one of the main people driving adoption of WSO2. In the beginning, we used WSO2 on virtual machines to handle the API and IAM requirements for more than 40 applications. Now we are currently in the process of migrating to WSO2 version 3 with Kubernetes as our orchestration system.
The principal things we use WSO2 API Manager for are to convert SOAP to Rest services, add security, and to provide more function for the administrators and to the developers. These are the main items. We now work with two versions which are in a test environment. We are using version 3.0 and version 3.2. It's very possible that the version that we will use in production will be 3.2. We can use WSO2 API Manager at IaaS and PaaS enviroments.
We use it along with IdentityServer, as our main API management tool for API exposure to the internet. It's not for internal usage, it's for external use. We have two main roles regarding WSO2 API Manager. There are the admins, who publish guides and user updates, etc — we employ around four people who perform this role. In terms of users, we have around five to six million users going through it on a monthly basis.
Business&Integration Arch Manager at a tech services company with 201-500 employees
Real User
2020-10-14T06:37:00Z
Oct 14, 2020
One of the main use cases for our organization is that we can use it as a digital integration hub. You can also use it as a base for a marketplace or open banking. We are using it for the enablement of a digital service or digital integration hub. We are helping small customers to digitalize their services. We select the best of these services and solutions and trying to deploy them in our platform and expose them to several different clients.
Chief Specialist at a manufacturing company with 10,001+ employees
Real User
2020-07-05T15:50:00Z
Jul 5, 2020
We use API Manager to publish our microservice for the public. We also use it because of its integrated functionality. We are researching many kinds of functions with WSO2, not only WSO2 management.
Chief Technology Officer at Swifta Systems and Services
Real User
Top 10
2019-08-01T05:43:00Z
Aug 1, 2019
Our primary use for this solution is to manage API, which is important to our business model and design of what we do as consultants. I found WSO2 (Web Services Oxygen Tank) was a platform that I could easily work on. All the building practices have to do with API, so when I needed a platform that could manage our API with flexibility, this was our best opportunity. It also leaves room for growth as a solution.
WSO2 API Manager is a comprehensive platform that allows organizations to design, publish, and manage APIs.
It provides a centralized interface for API governance, security, and analytics.
With features like API monetization and developer portal, it enables businesses to drive innovation and create new revenue streams.
I use the solution in my company as an enterprise application that will be placed in more than 175 places across the world, which would be in different countries. As an API management tool, it will be placed across different regions on Azure Cloud and WSO2's cloud.
I use the solution in the telecom sector.
We use the integrator.
We use the solution mainly to protect the frontend and backend proxy APIs. We also use the solution for federating with the identity server. We publish our backend API into WSO2 API Manager and use the proxy API outside. We use the solution for authorization, authentication, and accounting purposes.
We are using the solution for authentication purposes.
We provide this solution to our customers. Most of our clients are enterprise size organizations. We have a partnership with the company and I'm a solutions architect.
The solution is used mainly for API management.
Our primary use case is integration of legacy systems and channels, exposing APIs and security. I'm co-founder and CTO of the company.
We use WSO2 Manager for API management.
We are a banking solution and use WSO2 to offer our services to banks.
We use WSO2 API Manager for securing API calls for various applications.
We use WSO2 API Manager to manage APIs.
WSO2 API Manager is used for digitalization and innovation.
WSO2 API Manager is a complete platform for managing APIs.
Our normal use case for API Manager is to create pre-configured store users. The administrator who creates those users then sends them their credentials and secure links. We are running API Manager on a Tomcat server. Currently, I am the main person who works with API Manager, because it requires a proper understanding of the APIs.
We have developed a slew of applications for Bank, that helped transform multiple core banking processes, such as customer onboarding, account servicing, and rapid loan request fulfillment. The solution, which is powered by WSO2’s API management and enterprise integration technologies, seamlessly bridges systems while paving the digital path to a connected financial ecosystem.
We're currently evaluating WSO2 API Manager and Kong for development environments and not production environments. We're currently using Apigee and AWS API Database for the production environments.
I work as a software engineer on the WSO2 API management and WSO2 identity and access server, using version 2.6. At my company, Jio India, I have been one of the main people driving adoption of WSO2. In the beginning, we used WSO2 on virtual machines to handle the API and IAM requirements for more than 40 applications. Now we are currently in the process of migrating to WSO2 version 3 with Kubernetes as our orchestration system.
The principal things we use WSO2 API Manager for are to convert SOAP to Rest services, add security, and to provide more function for the administrators and to the developers. These are the main items. We now work with two versions which are in a test environment. We are using version 3.0 and version 3.2. It's very possible that the version that we will use in production will be 3.2. We can use WSO2 API Manager at IaaS and PaaS enviroments.
We use it along with IdentityServer, as our main API management tool for API exposure to the internet. It's not for internal usage, it's for external use. We have two main roles regarding WSO2 API Manager. There are the admins, who publish guides and user updates, etc — we employ around four people who perform this role. In terms of users, we have around five to six million users going through it on a monthly basis.
It is basically used for the integration of applications inside the organization and also for business partners outside the organization.
One of the main use cases for our organization is that we can use it as a digital integration hub. You can also use it as a base for a marketplace or open banking. We are using it for the enablement of a digital service or digital integration hub. We are helping small customers to digitalize their services. We select the best of these services and solutions and trying to deploy them in our platform and expose them to several different clients.
We use API Manager to publish our microservice for the public. We also use it because of its integrated functionality. We are researching many kinds of functions with WSO2, not only WSO2 management.
Our primary use for this solution is to manage API, which is important to our business model and design of what we do as consultants. I found WSO2 (Web Services Oxygen Tank) was a platform that I could easily work on. All the building practices have to do with API, so when I needed a platform that could manage our API with flexibility, this was our best opportunity. It also leaves room for growth as a solution.
Security and management API.