IBM API Connect Reviews

Our primary use case of this solution is as an API gateway. We are customers of IBM and I'm a  technology consultant.

This solution is very easy to use. 

Debugging could be improved, the solution doesn't really give a lot of debugging, and I'd also like to see an improvement in the analysis. 

I've been using this solution for four years. 

In general, stability is good, although there are very frequent patches that are required, and that is annoying.

The scalability of this product is good. 

The technical support is very good. 

The initial setup was straightforward.

Licensing is expensive but it's a good product. 

I rate this product an eight out of 10. 

We use IBM API Connect before API publishing for enterprises. If we have a big enterprise and they want to publish their data for the public, we use API connect.

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

The initial setup and installation could be easier. The price could also be better. I would like to see monetization of support, a monetization billing engine, and monetization within the product in the next release.

I've been using IBM API Connect for two years.

IBM API Connect is stable.

IBM API Connect is scalable.

Technical support is excellent.

The initial setup and installation aren't easy. It's complex.

One member of our team implements this solution.

IBM API Connect could be cheaper. We pay for the license yearly.

On a scale from one to ten, I would give IBM API Connect a ten.

Our primary use case for this product was doing a  project for the banking industry. We had to use it to help comply with PSD2 (Payment Services Directive) regulations.  

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.  

One place that I think the product could improve is that it could be lighter on computing resources and cheaper. We did not expect to have to add additional services for data processing.  

We have been using IBM API Connect for about one year.  

We had one problem with the security and data resources early on when beginning to use the product. The problem was mostly due to the fact that when we started using the product, we did not have any knowledge of its requirements or experience using it.  

We are mostly satisfied with the Technical support that we received. We did not have to interact with them a lot. 

I do not deal directly with the area of budgeting. We are partners with IBM, so maybe we get different pricing. I do not know about standard prices other than that this product can be expensive. We did not need to pay them anything extra for support or add-ons. It may not be the same for clients who are not partners.  

Initially, we did not do any exhaustive research on competing products. We are looking at the market more in-depth now. I think that API Connect is too expensive for us. For some companies that have a higher demand for using this type of product, this may be a good solution. We do not have a lot of projects of this type, so we are looking for some other solution that is cheaper for the long-term. It has to be good enough and have the proper security constraints to meet client needs. Our research into other products has not really narrowed the field yet.   

On a scale from one to ten where one is the worst and ten is the best, I would rate IBM API Connect as an eight-out-of-ten comparing what I know to other products.  

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.

The gateway is the most valuable aspect of this solution. 

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

In terms of what needs improvement, some of the product documentation could be better.

I have been using IBM API for around a year.

I haven't had any issues with the stability. There are around 1,000 users using IBM API in my company. 

Their technical support is okay. 

I would rate IBM API an eight out of ten. 

I would recommend it. I'd say that you need some time to negotiate the documentation and the conflicting support that's on their website. The website will day to do one thing and in another place, you do something else. You need some time to negotiate that.

Extracting the data could be improved.

My team members sometimes find it difficult to get something out of this solution.

I have been using it for the last year.

We have no issues.

The scalability is good.

The technical support is good. Whenever we need anything, we have our IT team work with IBM to change whatever requirement is needed.

I previously used the IBM Tivoli Monitoring tool before joining my company.

The initial setup was straightforward.

The pricing is too expensive with IBM. Sometimes, we prefer to go with an open source or something more lightweight.

I can recommend this solution and would rate it as an eight (out of 10).

We have done many implementations using API Connect. We work with some of the largest financial institutions in India, including life insurance companies and some of the banks. 

We have done most of them on-premise. The customers, because they are financial institutions and insurance companies, prefer to have this on their own premises and their own data centers.

It allows enterprises to expose some of their tech to outside stakeholders.

We have been implementing solutions with IBM API Connect for five to six years.

I would like to see automation of the installation. If there could be a single-click function where you could automate everything, that would be helpful. There should also be tools to automate the migratation from the older versions to the newer version. That would be another point that would bring my rating of it closer to 10 out of 10.

IBM sets the pricing, but it would be a good idea to bring down the pricing by at least 20 to 30 percent.

I would certainly recommend IBM API Connect for clients who are going with an enterprise version of implementation and when they have enough budget. Of course, if they have budget limitations, they can consider open-source solutions.

As implementers, we have a big resource pool here in India. All our associates have expertise with API Connect as well as IBM App Connect.

As of now, it is serving the needs of our customers. It is quite a proficient tool. It satisfies all of our requirements.

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).