Unlike conventional API management platform providers, WSO2 API manager gives you the power to host your own API management server with almost unlimited configuration options and possible integrations.

The WSO2 API Manager provides you with the capability to have your own API management server with a plethora of features; Swagger documentation integration, the ability to define your own API products with different payment tiers and throttling, and even integration with various authentication methods. Best of all, it's all free. You can simply download the API Manager from their website and get it up and running within minutes, and it provides many out-of-the-box integrations.

It can be hard to understand how to get some of the configuration options for the WSO2 API Manager working, and even more difficult to configure it to suit very specific use-cases that don't fit its out-of-the-box functionality if you are not an expert in using it.

The open-source API gateway solution from WSO2 is a compact powerhouse that competes with the corporate giants like APIGEE without missing a beat. The Sequence driven API management helps in all aspects of the API life-cycle. The throttling is powerful and can be controlled via automated deployment mechanism. The deployment is simple and straight forward and has multiple options to control the flow of the API and auto recovery features in case of an endpoint suspension. It is a robust product with pretty intuitive development scene.

Ease of Use Functionality Performance Scalability Security Options Availability Open-Source

Sync Issues Connector compatibility Deployment Screen issues/bugs Limited publishing options

It is easy to install and learn faster if one had knowledge/worked on a similar integration tool

Documentation should be improved and provided with more examples

WSO2 APIM won me a lot of time instead of going back to the Backend Team to change or update the API, I do this modification only at the API Manager level, so I don't need a software developer to update and repeat the tests on the Backend again.

I have tried many API Management solutions as (MuleSoft ,Apigee and SoftwareAg ) WSO2 was the best among them, as it is characterized by a clear and large documentation, as well as the people you will find when inquiring on StackOverflow Collection .As he is the only open source API Management , one of its advantages is that even if the functionality is not implemented and released, it allows you to develop it and use it by implemeneted a new interfaces.

Until now WSO2 APIM doesn't suppot RAML specification .Artificial Intelligence capabilities implemented until now, need to be more improved.The documentation need to be implemented with real samples .

I've trained 100+ people in using the API Manager and it is my favorite of the 4 products from WSO2. IT works with all of the other products from WSO2. (IS as external Keymanager, EI as the mediation engine), BPS as the workflow engine) and Stream Processor (as the traffic manager and / or Analytics Server).

Where shall I start? It is one of the big 4 of WSO2 and a product suited for the frontend management of APIs. You could say it is like a guard that will let people or not, but then of course with API's (but also Soap Services and Websocket services). It is hard to focus on all features (my YENLO WSO2 API Training is 3 days and really is the tip of the iceberg). It downloads as a monolith and can be used as that but has 5 components : store, publisher, gateway, traffic manager and key manager. It uses a store concept where users (read: developers) can find, try,rate and subscribe to APIs. The definition of the API's is done in the Publisher where technical details as well as search and explanatory details are filled in. When you invoke an API it is done through the gateway. In essence it is a mini ESB / WSO2 EI since the synapse configurations are basically the same as the Enterprise Integrator. Both of them are SYnapse configs in XML, the difference of course is that the API manager is more extensive. What is great is the extensible lifecycle of the API Manager. This allows you to extend the lifecycle that an API goes through like created, published and deprecated. There are so many features that i did not describe. IT would have been a big review if i did.

Like with the ESB, the Synapse / AXIS2 components are 10+ years old. Those need to be replaced so there will probably be a migration process in the future. It does not mean the product doesn't function but the components are end of lif That is why we see the next version of the API manager (3.0.0) being developed but also the micro gateway now in version 3.0.1 (using ballerina as the language). Any product has its pros and cons, the API Manager is no different.

Overall my experience has been excellent; the product is fully featured with the capability to handle nearly any outcome. I'm intending on extending it further with a few more interfaces as well to fill out our range.

Basic APIs are fantastic and able to be created in seconds. With a little bit of work it's possible to develop an entire suite to a pattern that is secure and robust. The scalability also is incredible; there has been a huge amount of though put into the solution as a whole to allow a huge TPS load with multiple tenants, all scriptable/API-driven. While I haven't put it truly through its paces, it's difficult to find a use-case it couldn't manage. Additionally being able to deploy WAR files directly has come in extremely useful. I've used this for stubbed functionality that the prototyping component can't cater for and it works incredibly well.

Like with any software this complex, it comes with a learning curve; the tough bit for me was the mediator components, which given how critical they are, felt a little hidden away. These items were also skipped over in the mini tutorial you get presented when creating an API for the first time, so take some digging into the documentation to understand their function and how they click. In saying that, they are extremely powerful; once you learn the nuances of how they fit together, it's insane the capability you're able to perform with them. There are a couple of items that do have some gaps however: - The Eclipse interface while powerful, feels clunky and slow. The drag and drop is great however if a little undocumented within the eclipse interface. If this were instead implemented within the product itself as a HTML5 interface "Gliffy style", it would be a fantastic integrated feature. 95% of the other Eclipse components aren't applicable to the API Manager anyway. - An online catalog of mediators that others have built would be handy, the sampled definitely give a good look and feel, however to take community created components and implement them into your own mediators saves the duplication needed.

At Whirlpool we use WSO2 APi Cloud. WSO2 provides API management system as SaaS. There we deployed our APIs that are being used and improving our businesses, partners, integrations, documentations and governance. On API Manager, we can deploy APIs, control their access by roles, follow up user calls besides the features of analytics and alerts that the tool provides.

The way we can expose our APIs, the way we control users and can expose our data using APIs. Basically we can create APIs, applications and have it available 24 hours a day.

The dashboards on API Analytics could be better. They are so "raw" and sometimes not easy to understand. That's why we use Grafana.

Digitalization programs

The solution is complete from API to Identity management and the product really offers a way to manage the customers of the API. The trafic and analytics rules can cover anything you need. It can integrate into simple to very complex security architecture. It can be setup in a few minutes to start with. It really comes with a API Store ready to build an API Marketplace.

The documentation si often short sighted. One can think it is a complex solution because of the adaptability.

I use this daily to manage APIs in our company applications. It is a very good tool in terms of functionality, but needs improvements on User Interface.

Publishing an API is very easy with only a few pages of configurations. Providing access to users based on application tokens and subscriptions is really good.

The user interface needs improvements. API search functionality is very bad, where keyboard shortcuts do not work. Only mouse clicks work.

This API manager helped us to design and publish lot of in-house and third party API's (Around 100) to the portal. Without this WSO2 API manager we won't make it this far. Thanks WSO2 for your support. Hooray...!

01. Its very easy to deploy and manage API's with this tool. We had deployed 100 of API's by using this WSO2 API manager. 02. It's very easy to install and run API manager. 03. It doesn't target a single platform. Either you're a windows user or Linux, Mac user you can easily use this tool to manage your API's. I have used it on Linux OS. 04. Simplest and coolest UI i ever seen. It's very attractive. This is very useful to get familiar with the tool in very short period of time. 05. If you are new designer, this tool will helps you to design your API's without any complications. And also you can publish them in a second. 06. You can simply monitor all your API usages without any worrying.

01. It's better if there are better way to see each node status easily. 02. Its better if they provide better support to users.

WSO2 is not for companies who want quick results from start. You need your organization - not just developers, even directors to get their hands dirty when need comes. It takes time to mature - then you can expect good results.

- Extendable: Given the open source nature, product team gave umpteen hooks for extending the capability of the product. E.g. API Life cycle phases and progression, Custom analytics, Workflow for publishing, and so on. - Customizable: Not simple UI level customization, ability to add custom connectors, custom mediation logic, and so on - Flexible: Product platform as such is deployable in multiple format and can be heterogeneous scaled

- Learning curve: Team implementing WSO2 has to go through a harsh, steep learning curve. For a starter - there are no starting place. When compared to competitive products - ApiGee has 4 min videos, Mulesoft has online training course, Boomi has detailed tutorials. - Documentation: It needs a complete makeover - it does not have a flow, nor its easy to navigate. Samples provided as mere code - needs an explanation - Community: WSO2 product developers write multiple blogs - that is the only savior. If you are in search of some technical question - google is of little help. You do not have a place to start searching. support.wso2.com needs to have some capability to up itself in google index

Overall its a great product. We have deployed all of APIs behind a VPN and expose them only thru API gateway. Deploying a all-in-one single instance is easier in a container, but gets tricky when deploying in a distributed clustered environment. Easy to customize the UI if someone is looking for white labeling it.

It offers several features out of the box for an API gateway. From defining an API to publish and use both for internal and external consumption. It has tight integration with Analytics module to give several key metrics of API usage.

Setup is bit tricky. Also publishing the API requires volume mounts and in a cloud deployment it may seem easier but gets real annoying if we have to republish an API. When only one instance is running and it goes down, restarting the gateway requires all APIs to be republished.

Throttling and Analytics was the most important feature I would highlight with. Our solution required very granular level of throttling setup with various tiers and WSO2 API Manager really helped us to achieve the limits we wanted.

Setting up themes was bit difficult and one more important issue we faced was setting SSL certificate for the same. Though we could set up the certificate, few of the store pages would open up using local IPs with in secured certificate errors which we could never rectify. We finally stopped exposing the store and we used it intranet for subscription.

Overall I am pretty much satisfied with this tool. We are successfully defined and implemented the System,Business and process API's with our client. Performance and scalability is awesome compared to other tools.

Performance and functionalities are very good and ease to use the tool. We have been using in our current project to integrate the different client end systems. Compared to other API tools in the market WSO2 API manager is easy to install and configurable. And it is available in both PAAS and IAAS level solution.

Did not able to communicate with BPS from the API manager that is least like about this. Need to come up with the more customization.

- We have services created in many different back end technologies, WSO2 help us to connect to all of them with a single end-point. - WSO2 manage applications security and role based access for our apps. - WSO2 can wrap SOAP service and create REST service for us. Which is nice.

The upgrade. Each time we upgrade something broke. Would be nice to keep backward compatibility. But I understand sometimes to make it better we have to get rid of the older bad stuff. I like the old UI better. The old UI is more intuitive than the new one. Well to me at least.

Our experience is good. We outsourced the process of installing and configure the product to a local expert and is going well.

It is very intuitive, easy to get started and to build a simple scenario. It has lots of features and is very well designed to handle security.

If you need to do different things from what the out of box product can, it is very hard. Existing documentation is good but just to get you started. I think support from WSO2 is very expensive and almost impossible for small to medium sized companies. They should have intermediate packages for those cases

This application is open source, very reliable and lightweight. Actually It helped me to gain my skills and knowledge about handling API's within very short period of time. Any type of user can easily work with this tool( It comes with tutorials ). I have couple of years of experience with API management and this is the best choice I ever made. If you're using this amazing tool, it's not difficult to deploy and manage API's anymore. It comes with API store, API designing & deploying functionalities, user permissions, security controls, usage monitoring functionalities and many more.

Actually it gives me all the required features to manage my API's properly. So I didn't have any cons. Amazing application.!

I had good experiences using WSO2, we set a default for ours APIS. We developed some Mocks and control better the versions of ours APIs. The Store is very useful to provided for ours partners the swagger and documentation of APIs.

It´s easy to install on a local environment and it´s very easy to develop some Mocks before the web services are ready.

I think the swagger editor could be more practical, to maintain the API.

WSO2 API Management solution is used in one of the projects to enable API Access Control using in-built Auth Provider, publish, discover and subscribe APIs using simple, elegant, intuitive in-built Portals. Besides that, WSO2 API Management solution offers support for caching, traffic control & version control like every other API Manager at an enterprise grade but under open source umbrella. Though the product can be used free of cost under open source licensing, it is recommended to get a subscription which brings in a lot of support & services including early security patches and upgrades.

The ease of use. Availability of documentation and support for various authentication schemes. Easy installation and product configuration. The product is up & running in less than 5 minutes.

Licensing terms could be slightly simpler to understand. Subscription and licensing appear slightly expensive like other commercial products.

We use WSO2 API Gateway for publishing and consuming our APIs. Easy to work with and customize as the code is open sourced. Built-in Swagger like console makes it easier to try our the APIs.

The UI is sometimes laggy, things need to be improved in UX point of view.

The product is open source and easy to learn and easy to use, It has so many components like ESB, APIManager,IdentityServer,SmartAnalysis. Finally it is flexible,powerful.

Documentation and videos are vary less to find.

IT ease to create and publish the API's

I liked the way that they have build the software

The support need to be proactive and the proper support should be given

This is easy to use but it can be more user friendly.

Sometimes, it becomes slow and doesn't bring changes as required.

Overall a good tool for integration services.

1) User friendly interface 2) Easily understandable 3) Good documentation

1) Debugging can be improved as logs need to be depended upon every time

Fits our requirement around API lifecycle management including effective client apps onboarding and client SDK generation for client apps. Post-production support from the vendor (WSO2) was excellent.

We are using the API Cloud from WSO2 and there is no better visibility of log files as it was multi-tenanted. Message tracing and debugging was an issue for us.