IBM API Connect Reviews

We have implemented this for four or five banks in Nigeria. The bulk of our clients are banks. We need determine if there are transaction capabilities from their back-end applications. If so, then we consume their APIs. For example, we have a logistics company who uses the bank's back-end API to complete their payments.

We specialize in application and cloud integration. 

We have clients deployed on-premise, on the cloud, and with hybrid cloud.

The workflow allows for different parties to work independently of each other, e.g., business people can work independently of the developers. 

If the rules are well followed and aligned, an organization can run a constant API ecosystem.

Our version supports containerized integration. I can write APIs, which can be moved into a testing environment without needing a forklift. It can check if APIs are compliant before moving them into production. 

API Connects has absolutely helped to reduce the time it takes to deliver new integrations to my clients. Integrations are a lot faster, which is a big selling point, as it reduces cost on the front-end.

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.

There is room for improvement in the reporting and monetization. With monetization, I want to be able to provide my own pricing and platform.

I would like them to add hooks into the API. E.g., it should be able to check credit, then limit access to people who don't have credit anymore.

They need to have more training for people. 

Since 2017.

There are issues with upgrading in the cloud version. The cloud version is extremely buggy. We prefer to use the on-premise version.

It's redundant so scalability is not much of an issue.

I would rate their technical support as a five out of 10. They are very slow. IBM has been working on this for three years. 

Some of our clients tried to use a customer design. They switched to API Connect because it is more advanced.

The initial setup and development are straightforward. The cloud is already available, so the development is what takes time. Deploying the cloud just takes clicking. It can deployed in minutes. The on-premise deployment takes two or three hours without issues to set up. if there are issues, it could take a day to set up.

It takes one person to set up, max two, as it is straightforward. There is not a lot to do. The system admin will probably spend one to two hours on it to maintain it.

It takes us a week or two to set up 50 services in API Connect. The only thing that might take extra time is portal design because that requires us to go into the back-end.

API Connect is quite pricey.

The developer builds the API and determines what should be put together. However, the business people determine the price.

The product plan and pricing needs improvement. It is confusing to the client based on the way a business might put it together. E.g., I have to be able to pick out different APIs, then group them together. I then have to explain to the client if they subscribe to this API product all the services available. Many clients want a variety of price groups based on their API selection.

I haven't seen anyone go from on-premise to the cloud. In fact, I am seeing people go from the cloud to on-premise because the costs can quickly grow on the cloud. 

If you want to small small, start with the cloud.

The integration is quite fast compared to others. Other companies combine their API platforms, but API Connect is as straightforward as you can get it. 

Oracle doesn't understand the different personas that need to be defined. This is why API Connect is superior to it.

Microsoft is extremely cheap compared API Connect. We are reviewing their solution in comparison to API Connect.

The client needs to understand the service to use it. They need to make sure that they have the back-end infrastructure to support API Connect.

API Connect is known for its light front-end system. Therefore, it depends on what system it connects to on the back-end. It is important to know how it connects to the back-end.

We are not using Cloud Pak, as it is still too new. We are using it in the lab.

I would rate the solution as a nine (out of 10). 

We are using this solution to handle our open API Connection.

Our company mainly has cooperation with institutions, and we are hoping that with this product, in the future we can create easy connections to other institutions who also implement open API.

The most valuable features are stability and security.

The developmental process is not quite user-friendly.

IBM should improve the customization of the API Connect.

The price could be reduced, it's expensive.

I have been using IBM API Connect since August. It is not in production, we are still in the developmental stages.

We have just finished the procurement process.

IBM API Connect is a stable solution.

It's a scalable solution.

The number of users is not relevant. It is based on the number of transactions, not users.

We plan to continue using this product in the future.

IBM technical support is good.

Previously, we didn't use another solution. This is the first API management product that we have used. 

The initial setup is straightforward, and the installation is easy.

We have a team of ten technicians to deploy and maintain this solution.

It's an expensive product.

I would rate IBM API Connect an eight out of ten.

We use this solution for managing APIs.

The most valuable feature is the interface.

The capabilities are very good.

It would be helpful to have access monitoring.

The initial setup is complex.

We have used IBM API Connect in several projects over the past couple of years.

IBM API Connect is very scalable. Our integrations are typically with enterprise-level organizations or SaaS providers.

We normally rely on our internal team for support.

Most of the time, the initial setup is complex. Implementation will take from a few hours up to days.

I would rate this solution a nine out of ten.

Building APIs.

Still working on it.

I have found the API Management to be most valuable.

Business applications could be exposed to users.

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.

The biggest benefit is the availability provided to the people that will use my services. They can go to a portal and look for services to identify which ones they'll use.

We use it for existing IIB services. We call on multiple back ends from the same service where the record layouts are different. It's difficult to describe and use them in the product.

Actually, we're in production for demo purposes, so I really can't speak to this. So far, we've had no issues.

We have used technical support and we have a good response.

The decision to switch was made before I had left IBM and went to this company four months ago.

When selecting vendor, support and longevity are the most important criteria.

I was involved in portions of the initial setup. It was complex from the standpoint that there were a lot of components, but it wasn't difficult.

Make sure to understand its purpose and what it's used for and not used for.

We are using it for some applications that are useful for banking.

It is easy to use and stable.

It should be cheaper.

I have been using this solution for a couple of months.

It is stable.

It is scalable. We have around 1,000 users. We have a technical team of 10 to 20 people. They include managers and developers.

It is easy to install. It takes one or two days for deployment.

It should be cheaper. It has a yearly licensing.

I would rate IBM API Connect a nine out of 10.

• API management
• Securing enterprise APIs
• Metering
• Throttling
• Transformation
• Analytics
• Deployment on AWS

• Single entry point for enterprise APIs
• Basic OAuth
• Keys management
• Policy configurations are pretty easy.

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

Components, like caching, should be implemented as policies, not requiring dependency on an external solution. Apigee provides caching as a policy.

In-built policies and security functions.

Integration with DataPower as its API Gateway. Due to bugs in integration, we have to look for workaround on fixing and using DataPower as gateway. 

Have been working on this for three months.

We switched to APIC for easier management of APIs and to leverage its inbuilt policies, security features, and usage of DataPower as gateway.

Setup an "always and anywhere available sandbox" for experimenting and proof of concepts, because one will need to think and experiment much to use the tool.