IBM API Connect Reviews

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.

The APIs are exposed to B2B partners in a secured, and better way. Internal re-usability of APIs are encouraged by cataloguing all the APIs.

It lacks the ability for billing and metering the API usage to invoicing in v3, however, v4 does have this. Automation of deployments is needed.

We've used it over a year, v3 was purchased in Q2, 2014.

Manual steps for deployment is needed.

No issues encountered.

No issue with scalability as the run timefor API Management is proven and time tested i.e. Datapower which all fortune 1000 companies use.

The IBM customer rep was very helpful in the POC phase, and helped us escalate custom/new features which we requested.

Ir's excellent.

No other product was used, and the service was just exposed by Datapower.

Initial setup was straightforward as 50% of the solution was already in place. IBM API runs on IBM Datapower so the setup was only needed for IBM API Management itself.

We did it in house using the same set of Datapower developers supported API Management.

We also looked at WS02 which was way too complex and needed almost 14-15 VMs to run. As we had Datapower, it was a natural choice for us.

If the customer is already using IBM Datapower then it is a no brainer that IBM API Management will complement their existing investment.

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.

We are planning the usage possibilities of API management inside our company, and outside, as well. Plenty of our web services are spread throughout various enterprise infrastructures and we want to control them in a better way with this tool. Of course, the valuable part outside the company is possibility for tracking and exposing telco services, as well as a commercialization aspect, through a developer community.

We have no suggestions so far.

After six months testing the platforms we now have a preparation period for commercial usage. The platform is technically ready for use. We are using a Data Power XG45 v6.0.0.4 as the gateway layer alongside API Management.

No issues encountered.

No issues encountered.

No issues encountered.

We have no such information so far.

We know that our implementer had some problems while implementing the platform but the main vendors technical support (IBM) responded very quickly and professionally.

No, we didn't. This is our first tool with this functionality.

Initial setup is very simple. Later implementation is a little bit complex (disagreement of reference in documentation, different recommended OS versions for additional parts of the environment etc.)

The implementation team did it with the support of a main vendor team. They have high level of expertise.

No we didn't. Maybe ESB (Enterprise Service Bus which we already use) is one of the solutions for exposing different kind of web or other services for sharing usage data but we realized that API management will be more useful for our wider purposes.

It's a good solution with a simple user interface. It has many different possibilities as a business solution.

The seamless conversion between rest and soap and service catalog.

I am a consultant so I can explain how this product has improved my customer's organization: it has made it very simple to expose new services securely with a specific general policy in DataPower and also keeping track of their use (amount of calls, etc.).

Integration with Exchange Server. Also if it could be easier to configure or direct the DataPower policies that would help. I'd like to see a combo box to choose which processing rule to apply.

I've used it for a few months.

Only issue is with connecting it to Exchange Server.

No issues with stability.

No issues with scalability.

I did not require the customer service.

I did not require technical support.

It was an addition and not a substitution to anything.

It was straightforward.

Seems good so far, as it saves a lot of time. It used to take a long time to expose services, whereas now it's just a few clicks.

It's pretty simple, there's no need for any special advice actually.

I use IBM API Connect as a black box, I only consumed the APIs that it provides.

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

The solution could improve security and performance.

I have been using IBM API Connect for approximately two years.

I rate IBM API Connect an eight out of ten.