It acts as a central gateway for both external APIs and underlying systems. It's basically a central middleware for hosting APIs to the internet and consuming APIs from internal systems.

It provides central governance for any APIs going outside the network, ensuring security and a common contract for API definitions.

Its speed and performance are valuable.

The API lifecycle management has helped us to do the version controls and naming of the APIs. The product gathers data to measure API performance. Users monitor the utilization of each API and the response times. It helps manage the environment. The product facilitates development by allowing the developers to go to the portal and test the APIs.

DataPower Gateway holds significant value for us as it serves as the cornerstone of our enterprise security controls. Even in the absence of published APIs, DataPower Gateway continues to maintain robust security measures. In the event of IBM API Connect experiencing downtime, users can still access APIs through DataPower Gateway, thereby minimizing downtime and ensuring continued service availability for users.

IBM API Connect is a tool that helps enterprises to build an API for an enterprise. But we use it for user experience and channel integration. We use the features of building the APIs for the experience. API is exposed to different channels like mobile channels, automatic channels, portal channels, and different channels. We use the solution's management capability to define monetization and have different plans used to control IBM API Connect. So we use the full-fledged API management tool, especially for the development, monetization, publishing, and installation parts. Also, it's all deployed on an OpenShift platform.

It's quite flexible and easy to deploy, especially for beginners. It has almost all the features that an API gateway should have.

IBM API Connect is a reliable and scalable solution.

The solution provides a common place for all APIs, allowing for easy sharing and exchange of information between internal and external stakeholders. So, the solution functions as an API management platform.

What's best about IBM API Connect is the excellent administration. The development tool that builds the API is also very simple, and user-friendly, and it doesn't consume too much time.

Another valuable feature in IBM API Connect is its good reporting feature, particularly for operations, but the most valuable feature of the solution for the customer is security. IBM API Connect provides a DMZ and a security gateway between the external and internal environment, so you can publish your API safely.

IBM API Connect can also integrate with any tool or middleware that works on open standards without the need for development or coding, so integration with the solution is easier.

The most valuable features of the solution stem from the fact that it is very easy to use and is something that is easily configurable. The product actually provides a complete suite, consisting of the developer portal and management of the APIs, while giving access to a different set of users. The product also allows users to use API sandbox. Configuring the APIs with the backend systems is a valuable feature of the product. With IBM API Connect, I found everything to be very user-friendly, easy to use, and able to be developed quickly as well.

It offers enhanced security features to protect APIs, enforce access control, and secure sensitive data. It also works as a powerful integration tool for the internal and external transmission zone, allowing us to connect with different vendors easily.

The most valuable features of IBM API Connect are its performance and user-friendliness. 

One of the most valuable features is the easy-to-use web interface.

The most valuable feature of the solution stems from its ability in the area of message transformation, meaning it is very easy when you have to transform a message to XML or transfer it automatically from JSON and vice versa. The solution is very scalable. The solution works very well even if you have a small number of users. Our company also tested its use with a large number of users, consisting of more than 2,000 users, and it was very nice to use. The tool is very robust.

The older versions of the solution were fairly straightforward to install.

The solution offers a pretty good SLA.

We deal a lot with technical support and typically they do help. We need them as we often can't find the documentation that would help us circumvent their services.

I think the most valuable feature is the fact that it sort of combines IBM DataPower being a security gateway with some of the features that are in IIB and IBM App Connect, to kind of build a complete integration. Also, IBM API Connect being the API gateway is extremely valuable both for internal and external consumers of APIs. Off the top of my mind, those are the big points that I would add.

API Connect's most valuable features are API management and creation.

The interface is very nice. It makes the solution easy to use and navigate.

You can install it in coordinates, in general, and you can deploy it in Amazon, in Google, in the IBM cloud, or other clouds as well. You don't have to worry about having to work on a specific cloud. It makes it very flexible. This is very important.

The product is quite robust. 

The initial setup is very easy and the deployment is very quick. 

This solution is ready to scale and already supports our agile CICD.

One of the most valuable features of this solution is that it protects our backend system. We are exposing services to external parties and using this solution to protect the backend system, and to have a navigation in between. 

We really like the runtime capabilities of IBM API Connect. The creation of products and the control of the monetization and hit rate are some of the features which we've found very valuable.

One valuable feature of IBM API Connect is its role differentiation between API publishers and consumers. Publishers can easily identify, create, and publish APIs on the developer portal, defining plans, packages, and potentially billing rules. Consumers, interested in specific API packages, can subscribe, and use the APIs, and the platform tracks usage meticulously, allowing accurate billing applications for API consumers based on their usage patterns.

I have found IBM API Connect to be highly secure, efficient, easy to deploy, and has a great GUI. It can operate and integrate well with other vendors, such as Amazon, Google, and Microsoft.

The most valuable features are:

1. The centralized management: this provides a management module that can deploy and apply security policies to all APIs, including all the gateways that are deployed on-premises and on any cloud because the gateway component can run at a VMware or in a Kubernetes cluster.

2. The analytics module: this provides a variety of visualizations of the APIs, products, subscriptions, and applications that can be defined for a second, a day, a week, a month. This module is deployed beside the gateway and collect all the traffic.

The most valuable feature of this solution is to have the APIs available across different verticals in the company. IBM API Connect provides that capability for us, so as to expose the services as APIs.

Reusability is the biggest most valuable feature for us. The security is also a major feature in some ways because if it's in API Connect, the gateway, you're in and out, it's well organized, rather than having some internal solution where somebody has to manage the in and out. In API Connect, the certificates and all those things are managed pretty well. From a security perspective, it makes things easier. 

From an API perspective, it is pretty strong. Again, it all depends on how other teams are implementing like certificates. If you register you eventually have to request certificates which API registers, so it is secure. From that perspective, I think API Connect has a pretty decent product.

The most valuable feature is the security we get from this solution. I know of a bank that uses it to ensure that everything is secure. The second feature I like is the retail environment, where we actually want to be able to provide as many suppliers and consumers with APIs as possible. If you are well-trained in the writing of RESTful API's, you can actually publish an API in a matter of minutes, test it, and publish it.

It provides a good, simplified user interface to design and secure your APIs.

The most valuable feature of IBM API Connect is the security of the protocol.

In general, this is a powerful system. We're currently only using one or two functionalities from API Connect. One of them is consulting WSRR to get the endpoints which is a powerful component. Each API management has a Gateway located on the DMZ that can be exposed to external networks and does the authentication, authorization, some security functionality as filtering, checking the security aspects such as decrypting, encrypting or service transformation and other functions. The development portal is good and can be used by external developers who can develop it at their site.

It provides a few features such as security and discoveries.

The management of the API and API portal is good. 

When API Connect is running, it is a stable solution (just do not change it).

Also, managing products and catalogs was helpful and it would be helpful for (as in our case) companies that need to run a multi-tenant concept. 

The developer portal is based on Drupal which is in itself very powerful. The service provider view and the consumer view are totally separated (however - the look and feel are also different).

From a starter perspective, using OpenShift, the operators to install are all there.

The statistics component is easy to use. You get your information at your fingertip.

It gives a holistic environment for us to set up the APIs and that's the main value that it adds. It gives end to end for us.

API Connect's most valuable feature is its ability to act as a gateway. It's very easy to configure security and everything else in it. You don't have to kill yourself implementing custom configurations. Sometimes the customer wants to incorporate their identity provider, and API Connect handles that without any problems. 

The suite itself is what I find valuable. It has all of the tools that are needed for the specific mission. I have the portal, I have the run time and the security.

The solution itself is valuable.

The most valuable features of this solution are:

• Integration with multiple services,
• Providing security,
• Being able to monitor, and
• Enabling customers using the secure gateway.

We've yet to realize real value in the solution. The goals that we were trying to achieve from it were to implement microservices and a lot of the features and functionality that were part of the documentation, but we haven't achieved success with it yet.

The customer seems to really like how this particular solution works.

The solution is very stable.

The functionalities on offer are very good.

API Connect is a very good platform for the development of APIs.

Most of the business value that we are getting out of this solution, is that it provides DevOps integration and a catalog for microservices. We are able to share those APIs instantly within the organization; even if we want to share it outside publicly, then we can have those capabilities.

The ability for all of our web applications to share standard functions and documents easily is valuable.

The technical support and the user interface are good.

For on Premise Solutions:

Out of the box policies for Gatewayscript, JWT generate and validate. Oauth support .

Since it runs on top of Datapower, all Datapower based custom policies can be utilized and exported to API connect but its not straightforward/simple process.

Export of Analytics data in CSV format.

API connect is far better, faster and sleek as compared to IBM API management.

API connect support better error handling scenario with additional policies and catch node.

The most valuable feature for me is the ability to distribute work among our API developers, so we don't have to do all the work as IBM API Connect administrators and IBM DataPower administrators. This simplifies the way our partners can access our API's.

Overall, it brings us closer to better API management in our organization. The next step for us would be to improve the whole solution by going to the cloud. That's what I'm looking at.

API Connect's best features are its data gateway, one of the strongest in the market, and its API manager, which has the local assembly transformation UI, which helps transform services from Maximal to JSON or vice versa.

This product is well integrated with other products. Its ability to interact with IBM Secure Gateway and other products is the core feature. Also, the lead time to put it into production is relatively short and that is something customers are pleased with.

V3 is way better then v2, and v4 has further improvements. We have the ability to secure, control, transform, catalogue and optimize access to our APIs for external and internal partners and developers.

It is easy to use and stable.

This solution is very easy to use. 

IBM API Connect is a good product, and their technical support is excellent.

The developer portal has been the most useful feature.

• GUI-based accelerated API development
• Segregation of ownership and control for different stakeholders
• Self-service Developer Portal: a highly customizable portal based on Drupal CMS
• Security support for oAuth, basic authentication and keys
• Analytics
• High-performance solution when used with DataPower IDG. DataPower IDG can support 8K TPS per appliance
• Easy-to-implement, configurable API security and analytics
• LoopBack projects allow API creation using a datasource

This product has been designed very well and addresses many advanced use cases of API development in a collaborative environment, which are not yet available in other existing products, for example, Layer 7.

The most important feature is, for sure, the security gateway. But if we think commercially, the possibility for easily creating and exposing service plans and charging is also valuable.

API Connect is a good product, and everything works fine. All the analytics are good, and it is easy to follow up. I like it in that sense. I'm more focused on following up on analytics by seeing how many API calls we are getting and where we see a lot of problems. I was working on that API level.

The developer can connect to the back-end services and exclude APIs through API Connect. It is very robust, e.g., I can exclude web services. We can paste the code into the UI interface.

Pre-built connectors are good if you need more security, though it depends on the extent to which you use them, as they are not necessary to use.

The solution is very simple and straightforward.

The most valuable features are stability and security.

The most valuable feature is the interface.

The capabilities are very good.

I have found the API Management to be most valuable.

I like how it runs within DataPower, and adds the extra OAuth security. It gives me a common place to do security for all my API services.

One of the most valuable features is that we can seamlessly and harmoniously expose our capabilities, from a security point of view. 

• Ease of use
• Security
• GUI is pretty intuitive.
• Easy to configure security and generate API keys.

In-built policies and security functions.

It is a complete API solution for everything having to do with application development. It is an automated and all-in-one solution. It helps provide the API, expose the API, manage their exposure, and affect monetization. I have the operator portal, management portal, and analytics. This is the product I wanted, because I can do everything that I needed to with this one solution.  

The exception and error management have been the most valuable feature.  

We take steps for how many transactions we can create. It has a dashboard that allows us to see where transactions are coming from, which clients use it more, etc. This makes it very endearing for us.

The services that I consume through IBM API Connect are beneficial. It can handle multiple API management.

The seamless conversion between rest and soap and service catalog.

The gateway is the most valuable aspect of this solution. 

It has a good interface, dashboards, and monitoring tools.

As far as API Connect, I think it offers us more flexibility with our application and potentially would allow third parties to come in and develop for us. It also enables us to streamline our microservices journey.