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.
Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
173 reviews
from
and
External reviews are not included in the AWS star rating for the product.
IBM API to connect and interact
What do you like best about the product?
Easy to build an API by drag and drop way , any user can leverage the low code and no code powerful capability to build its own api . The api can be exposed to outside with just click several button
What do you dislike about the product?
No dislike but it can further enhance by being more useful products and capability
What problems is the product solving and how is that benefiting you?
Great way solving integration problem effectively. Salesforce can be easily interact with service now like n number of use cases can be solved
Hyper-flexibility Made Easy
What do you like best about the product?
Ease of implementation, flexibility of services
What do you dislike about the product?
Complexity for new users, expensive pricing plan
What problems is the product solving and how is that benefiting you?
Allowing to host multiple services and use multiple interfaces through cloud services
Amazing and next level experience
What do you like best about the product?
It is very easy to navigate and use. It is very adaptive and flexible. It is digital transformation for finance. It helps us govern our APIs and assets.
What do you dislike about the product?
A bit complex for beginner's, but amazing
What problems is the product solving and how is that benefiting you?
It is helping me to manage product life cycle. It's very flexible to use and easy to manage.
I had an amazing experience with respect to IBM API Connect.
What do you like best about the product?
The best what I like about API Connect was the analytics section, in diagnoising issues in production, our go to approach would be to check the API Connect logs. In the latest API Connect 10 version we had on our Cloud Pak. That version had the capability to show the processing time the request spent on each policy with in the API, so it gave us really good insights in identifying bottlenecks whether it was our gateway script or the downstream system itself and then take appropriate action.
The other feature was the capability of synchronizing data such as client ids and secrets. We had two seperate API connect deployments (Active and DR) and using the internal sub system backups of the main deployement and backup in the other cluster we were able to onboard one client and the same id and secret could be used in the other cluster, in case of enabling DR traffic.
Since most of our integrations were routed from the API Connect, it was a touch point for all the services for the organization so it was able to handle immense workloads.
It was also relatively easy to develop APIs and deploy it on the products. And with the role based access control we were able to make sure that only relevant users after review could publish the API's.
The other feature was the capability of synchronizing data such as client ids and secrets. We had two seperate API connect deployments (Active and DR) and using the internal sub system backups of the main deployement and backup in the other cluster we were able to onboard one client and the same id and secret could be used in the other cluster, in case of enabling DR traffic.
Since most of our integrations were routed from the API Connect, it was a touch point for all the services for the organization so it was able to handle immense workloads.
It was also relatively easy to develop APIs and deploy it on the products. And with the role based access control we were able to make sure that only relevant users after review could publish the API's.
What do you dislike about the product?
The only problem which I observed was where we had two deployments (Active and DR) running in two seperate clusters, we had issues of analytics availaiblity at one place, other than that there weren't any issues from the development and deployment perspective.
What problems is the product solving and how is that benefiting you?
The main problem that API Connect was solving was authentication and authorization, since we want the consumers to only access only those services for which they were provided the access to, furthermore the other direction which the organization was thinking was to use monetization capability with the API Connect to avoid API abuse by the consumers.
From the analytics perspective we onboarded the clients with perspective to business domain and region, so we were able to also have the stats on hand if the management team wanted to inquire the numbers for the calls from a certain region or domain or both.
From the analytics perspective we onboarded the clients with perspective to business domain and region, so we were able to also have the stats on hand if the management team wanted to inquire the numbers for the calls from a certain region or domain or both.
Helps with efficient role differentiation and has a valuable feature for analytical report extraction
What is most valuable?
What needs improvement?
The platform’s integration with the payment gateway needs enhancement. The setup process and support services could be improved.
For how long have I used the solution?
We have been using IBM API Connect for three to five years.
What do I think about the stability of the solution?
It is a stable product. I rate the stability an eight out of ten.
What do I think about the scalability of the solution?
It is a scalable product. I rate the scalability an eight out of ten.
How are customer service and support?
We encounter challenges related to the availability of local support and time zones.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We used another product for API management. However, there were several areas of improvement related to the availability of a knowledgeable and skilled support team.
How was the initial setup?
The initial setup is complicated for container deployment. It is easy to maintain. I rate the process an eight out of ten.
What other advice do I have?
We use the platform’s analytics feature for extracting reporting for billing purposes. It is a good feature. It offers a sandbox environment where users, such as developers or testers, can interact with and test various APIs.
In the subscription process, EVOFRO (Evaluate, Offer, Verify, Fulfill, Render, Operate) is involved, specifically during the consumer's subscription attempt. It triggers a flow that includes reviewing and approving the subscription. It helps us achieve 80% compliance with regulations for our company.
I advise customers to identify the use cases before purchasing the product. I rate it an eight out of ten.
Helps monitor and manage API services and measure the API performance
What is our primary use case?
We use the solution to monitor, process, and manage API services.
How has it helped my organization?
We use the product to enforce standards to check and align things with the application design. The tool has enhanced our digital transformation efforts. With the adoption of the cloud, we deploy a lot of APIs on Lambda. We also have APIs deployed on-premise. We use the front-end access of all the APIs on-premise and on the cloud.
What is most 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.
What needs improvement?
It would be nice to have a SaaS solution that can be deployed into the cloud.
For how long have I used the solution?
I have been using the solution for many years.
What do I think about the scalability of the solution?
The tool is very scalable.
How was the initial setup?
There's a bit of a learning curve to the setup process. Once the support team gets familiar with it, it is just like any other product.
What other advice do I have?
We started with DataPower ten years ago. Most of our APIs are SOAP APIs. When we started using RESTful APIs, we started using IBM API Connect. It took us a while to adopt API services. I will recommend the solution to people who need to manage their APIs. It's pretty good. It serves our purpose. Overall, I rate the product an eight or nine out of ten.
A decent API Management offering
What do you like best about the product?
The comprehensive set of tools for designing, managing and securing API's.
What do you dislike about the product?
The complex learing curve. IBM's tools and services are expensive.
What problems is the product solving and how is that benefiting you?
API Connect allows to me securely mange and design API's. I as a developer, leverage the visual interface to design APIs and define endpoints.
IBM API Connect - one solution for API Managmenet
What do you like best about the product?
Request and Response bodies can be changed to different xml, json formats. Also testing the API's are convienent
What do you dislike about the product?
UI /UX interface can be made more user friendly eg Postman
What problems is the product solving and how is that benefiting you?
Its helping us to test different API's we are developing and its integration with application. Good alternative to POSTMAN and reducing dependency
A complete package of tools under one roof.
What do you like best about the product?
-Multiple features such as api management, microservices architecure, REST/SOAP APIs handling.
-Subscription based model and platform independant and easy to integrate.
- Easily adaptable and available to use.
- Great customer support and escalations handled ontime.
-Subscription based model and platform independant and easy to integrate.
- Easily adaptable and available to use.
- Great customer support and escalations handled ontime.
What do you dislike about the product?
- Bad pricing marketvalue and low speed.
- Less number of repeat customers.
- Less number of repeat customers.
What problems is the product solving and how is that benefiting you?
- API Management -> Effortlessly manage and monitor all of your APIs from a one location.
Automation engineer
What do you like best about the product?
Good the IBM api to fetch the details using title and some details related and respond faster
What do you dislike about the product?
Basically i am developer and i not fscing any issue like disadvantages
What problems is the product solving and how is that benefiting you?
I using API for the some testcase write or any script created for automation and development then useful for me
showing 31 - 40