Based on 8 verified reviews published in the last 18 months
TrustRadius Community Insights are summaries of user sentiment data from TrustRadius reviews and, when relevant, HG Insights data.
Overview
Synthesised from 8 reviews | Last Published May 27, 2026
IBM API Connect serves organizations primarily for comprehensive API lifecycle management, overseeing APIs from initial design to retirement and transforming traditional handling methods. Reviewers widely note its robust security features, including rate limiting and threat protection, as a key strength. In TrustRadius reviews, the platform is also valued for its comprehensive API management and configuration tools, user-friendly developer and admin portals, and integrated analytics for monitoring performance and usage.
While the platform contributes to reduced API development time and improved operational efficiency, a recurring concern is the complexity of its user interface, which can present a steep learning curve for new users. Performance issues, such as slowness during API import or editing, and a high cost structure for certain features are also reported. Despite these challenges, the platform is generally viewed as effective in enhancing security and governance, contributing to a positive impact on business objectives.
Pros
Robust API security features, including rate limiting and threat protection
Comprehensive API lifecycle management and configuration tools
User-friendly developer and admin portals for navigation and management
Integrated analytics and monitoring dashboards for performance insights
Support for API productization with various pricing plans
Cons
Complex user interface with a steep learning curve for new users
Performance issues, including slowness during API import, viewing, or editing
High cost structure for certain features, leading to scaling back usage
Challenges with OpenAPI data validation, particularly with regular expression syntax
The tool is effective for the creation, assembly, management, protection, and sharing of the programming interfaces of web applications. It can cover all the phases of the API lifecycle and be accessed by different users, allowing good management of all the processes. Usually, these processes are not managed through a single platform; therefore, tracking the status and collaboration could be complicated.
Pros
It covers all the phases of the API's life, from generation to publishing.
It allows multiple users to access and have a single source of truth about the status, open points, and owners.
It can support multiple APIs simultaneously, allowing different teams to work independently.
Cons
Improvement can come in the interface of the tool, which is sometimes complex and requires a deep understanding of the tool.
Improving the different levels of access to the playroom could be helpful because product owners and developers need to see other information.
Publishing API and integration of API can be more straightforward.
Likelihood to Recommend
It is well suited for the development of API from scratch, using the tool from day one, since its conception, tracking the development, the tests in the different environments and the releases, and keeping all information in just one platform. It is not appropriate for gathering requirements and defining objectives.
VU
Verified User
Project Manager in Information Technology (10,001+ employees)
API Connect acts as an exposure layer (ingress point), fronting our integration bus services components. Providing a TLS termination point, authentication, fine grained authorisation, and rate limiting capabilities.
Pros
Open API Specification authoring
API and API Product lifecycling
Self service
Cons
Adherence to industry standards e.g. W3C SOAP specifications
Validation policy breadth and depth
Full OAS support
Likelihood to Recommend
Well suited scenarios: Use as an API gateway, ingress point for ReSTful HTTP(S) interfaces / services. Less appropriate: Use as an API gateway, ingress point for SOAP interfaces / services
We use IBM API Connect as a company-wide API management solution to connect provider and consumer applications between cloud and on-premises environments, bring transparency to integration and APIs, to monitor API usage and to secure API traffic.
Pros
API product management
API subscription management
API security
Cons
API portal for multiple catalogs
API dev tools (API Designer)
API deployment pipelines
Gateway stability
General product quality
Likelihood to Recommend
Cloud to on-premises communications
SOAP to REST and vice versa
Subscription and API product management features
VU
Verified User
Consultant in Information Technology (10,001+ employees)
IBM API Connect is being used by a few departments. Since we run our backend services in IBM Cloud, we choose IBM API Connect as the API gateway solution. It provides the routing rules, security, and rate limits before the calls can reach our backend services. We also use its analytics feature to get more insights.
Pros
Enhanced security with client id and client secret features.
Easy to deploy API changes through automation.
Good UI to manage APIs.
Cons
Sometimes we see issues after deploying API changes, re-deployment can solve it.
A bit hard to troubleshoot issues if the calls do not reach our backend services.
Likelihood to Recommend
From our experience so far, API Connect is very stable and scalable. It can handle our peak traffic without any issues. It is well suited as an API platform that requires API versioning, rate limiting, authentication, security, automation, analytics, etc. It has both cloud and non-cloud products with different features. You can use it with non-IBM Cloud services.
I use IBM API Connect to help customers implement API First Strategy. IBM API Connect helps discover the APIs in the organization and help manage lifecycle of APIs. It helps in socializing the APIs with wider range of audience within organization as well as it helps to expose APIs to external world. Developer portal helps partner onboarding easy as partners can try out the APIs before actually entering into contract with the clients.
Pros
API lifecycle management
API Discovery
Developer portal experience
Cons
More visualization in how policies/APIs and products are being connected
Simplify the components or at least better visualization of IBM API Connect subsystems like API Manager, Analytics, gateways
I think we can simplify the GUI and jumping from developers portal to analytics to API manager etc
API automated testing
Likelihood to Recommend
IBM API Connect was really helpful in creating proxy API layers around functionality implemented in ACE as well as other applications. API security features were easy to implement. It was not suitable tool for transformation of he messages - the functionality is limited but that is understandable. Overall for converting existing application into API and exposing them internally or externally securely was important use case for IBM API Connect.
Verified User
Director in Information Technology (10,001+ employees)
