Coming October 25: PeerSpot Awards will be announced! Learn more
Julia Frohwein - PeerSpot reviewer
Senior Director of Delivery at PeerSpot (formerly IT Central Station)
  • 0
  • 6

What is your primary use case for IBM API Connect?

How do you or your organization use this solution?

Please share with us so that your peers can learn from your experiences.

Thank you!

PeerSpot user
19 Answers
Consultant at Bancolombia
Real User
Top 5
16 April 21

We primarily use the solution for a bank. It's used for the operations portion of the bank. It's primarily used for the review of the personnel in your accounts et cetera. It's for many operations for the bank.

Associate Director, Cloud Architect at a computer software company with 5,001-10,000 employees
Real User
Top 10
26 March 21

The solution is primarily used as the API gateway. It's for the application that performs the function as the API for the consumer.

Manager Integration Platform Engineering at a insurance company with 10,001+ employees
Real User
Top 10
25 March 21

Right now, our use cases are all internal. It's all API socialization internally. With version 10, we'd like to go externally with an actual API marketplace, however, we haven't gone there yet. I don't publish; I manage infrastructure. My role is to implement the infrastructure, maintain it, and enable the developers to leverage the technology.

CTO & Application Infrastructure Manager at a financial services firm with 1,001-5,000 employees
Real User
Top 5Leaderboard
05 March 21

We use this solution for external API spotters and API.

SOA & BP Technical Manager at a tech services company with 1,001-5,000 employees
Real User
Top 5Leaderboard
10 February 21

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.

Core Banking Business Analyst Manager at a financial services firm with 1,001-5,000 employees
Real User
Top 10
28 December 20

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.

Learn what your peers think about IBM API Connect. Get advice and tips from experienced pros sharing their opinions. Updated: September 2022.
633,952 professionals have used our research since 2012.
Lead Architect at a insurance company with 10,001+ employees
Real User
Top 10
11 October 20

Our use case for this solution, depending on the API Connect centralized team, is for registering any APIs. Once those are there, the main idea is that they have to be reusable and available like a global platform rather than just internal to your applications. API Connect does that, you register your API and it is available. Anybody who wants to use that function or that API can now go through API Connect with the current credentials and get access to your API. I'm a lead architect and we are customers of IBM API Connect.

Team Manager at a tech services company with 51-200 employees
Real User
17 August 20

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.

German Villar - PeerSpot reviewer
Director of Development and Innovation - CTO at Cofares
Real User
30 June 20

We use this solution for managing APIs.

Alexis Aguiluz - PeerSpot reviewer
Senior Technological Architect at Banco de Chile
Real User
Top 20
26 May 20

The API manager of the enterprise exposes common functionalities to the front-end applications, beginning with the frontend of the executives who access clients' information. The exposition of the functionalities of transferring funds and AFP which need to transfer the money from your account to a client's AFP. The exposition of the core functionalities to the module of the sale of a product installed on the cloud of AWS, to create an onboarding platform for the client's prospect of the enterprise.

AdemolaOsindero - PeerSpot reviewer
CEO at Lopworks Limited
Real User
29 March 20

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.

CTO at a tech services company with 51-200 employees
Real User
25 March 20

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.

Clement Hsieh - PeerSpot reviewer
Doctoral Researcher at NCCU
Real User
25 March 20

We help systems integrators and vendors in choosing different types of platforms for building an open API gateway for banks. We evaluate and test different types of API gateways. We follow our internal testing scenarios to make sure that the product meets requirements. This is all we do.

Augustine Ayo - PeerSpot reviewer
Middleware Solution Architect at a tech services company with 51-200 employees
Real User
25 March 20

We are a financial services provider. We have services that we expose for things like investments, policy management, and so on. We have put this on an API Gateway to be able to aggregate all the things that we do for different types of clients with whom we engage.

Open API Consultant at a tech services company with 11-50 employees
18 July 19

We primarily use this solution for the regulation of open banking.

Oladipupo-Aina - PeerSpot reviewer
Engineering Technology Services Manager at a financial services firm with 1,001-5,000 employees
Real User
16 July 19

We currently use it as our single point of the security catalog for the APIs that the bank has.

Senior IT Operations Engineer at a retailer with 1,001-5,000 employees
Real User
16 July 19

We primarily use the solution for distribution.

Manager at ANDD Techservices
05 October 18

Building APIs.

Amnesty International at Gfi Informatique
11 July 18

This solution is primarily used for workflow applications. Specifically, it is used for web applications with complex workflows that have many users.

Related Questions
User at Santander Bank
May 02, 2022
Hi community, I'm researching API management solutions. My use case: using a microgateway in containers. Should I choose IBM API Connect or Apigee? I'm not able to see the API Connect's value. Tnx.
See 2 answers
Evgeny Belenky - PeerSpot reviewer
Director of Community at PeerSpot (formerly IT Central Station)
16 November 21
Hi @Pradeep Pavuluri, @Bert Van Vugt ​, @Balakrishnan Vinchu, @Carlos Maximo Ramos, @Clement Hsieh, @Augustine Ayo ​and @Irshad Ahamed, Can you please chime in and assist @Pepe Redondo Rubio? 
Walter Kuhn - PeerSpot reviewer
ICT Architect at a tech services company with 51-200 employees
02 May 22
We are using API Connect for approx. 10 months. It has been (and still is) a very stony road. We are now considering another solution. My findings w.r.t to API Connect: Pros:  - Concept of catalogs is useful (for us) w.r.t. dealing with several tenants. - When it is running, it looks very stable. Cons: - Installation and updates were a nightmare each time. We use OpenShift; and we had problems for up to three weeks for an update, including support from IBM. We cannot afford that in production, which leads to investigations on our side. - Small amount of policies, compared to some of the competitors. In the current version, a "map" is not supported (according to IBM). - No debugging of the flow. - High footprint of pods and resources, compared to an alternative.
Nurit Sherman - PeerSpot reviewer
Content Operations Manager at PeerSpot (formerly IT Central Station)
Mar 23, 2018
One of the most popular comparisons on IT Central Station is Apigee vs Mulesoft Anypoint API Manager Which of these two solutions would you recommend and why? Thanks! --Rhea
2 out of 7 answers
it_user521277 - PeerSpot reviewer
Technical Lead at hcl
22 March 18
I have worked on 5 API products each product has its own pros & cons. I would choose Apigee over all others because it provides pure API Management Tools & Services. Apigee also provides a lot of OOTB Policies which can be applied with little or no change. API Development & Exception handling is too easy in Apigee compared to Mulesoft. Go for Mulesoft if ESB capabilities are required and unlike APigee we can do a lot of customization & create custom policies in Mulesoft. Mule also provides a lot of third-party connectors OOTB which can be used to quickly integrate with other systems. We can also create custom connecters as per our requirement. Apigee supports Swagger & Mule supports RAML. So if your existing services/APIs produce/use Swagger go for Apigee. Anyway, we have many scripts which convert Swagger to RAML & vice-versa. A very good Developer/API Portal is required for exposing the APIs securely & well-documented. If this is an important requirement, I would recommend Apigee over Mulesoft. Apigee's Drupal-based Portal provides a lot of features which Mulesoft Portal lacks. Apigee also provides features/tools on Analytics & Bot-Detection for improving your APIs consumption.
it_user783168 - PeerSpot reviewer
Enterprise Architect & Principal Consultant at a tech services company with 10,001+ employees
22 March 18
It depends on your needs. I would recommend Apigee if you are don’t need an Integration Platform/ ESB for any heavy lifting. Mulesoft Cloudhub comes with one common engine “Mule Anypoint Runtime Engine” which is the core and offers ESB capabilities including a lot of OOTB connectors. Now if your southbound/ downstream has a lot of legacy applications requiring message/ file based integrations, then it makes sense to use Mulesoft, wrap these legacy-interfaces as HTTP/Web end-points and wire them using API Manager. On the other hand, if you downstream is already on HTTP endpoint/ microservices, then Apigee is far more robust than API Manager. You can simply scale it to 200tps without any hassle. The deployment model of Apigee is lot cleaner as you can scale the “Message Processor & Message Router” (part of Edge gateway) separately from Dev Portal & Management server. The analytics is far superior to Mule and you far more options when wiring API than Mule. For example, the concept of IP-whitelisting, data policies (as filters) is pretty cool in Apigee. Another key point is you can have a hybrid model in Apigee with on-prem Message Router(s) to deploy multiple clusters of microservices. I have not used BaaS but it gives you the ability to create “Application Network” very similar to Mule except it looks richer. Finally, with zookeeper, clustering of Apigee Edge server is more robust than Mulesoft, especially on higher loads. My verdict is Apigee if Integration is NOT a need. BTW, I felt API Manager’s Anypoint Exchange is a better collaboration platform for sharing API definition within enterprise and outside. It's actually nice ?. But with Salesforce acquisition of Mulesoft, please understand their long-term roadmap and support/upgrade (especially if you going with On-Premise and not on cloud). Best Regards, Arnab.
Related Solutions
Download Free Report
Download our free IBM API Connect Report and get advice and tips from experienced pros sharing their opinions. Updated: September 2022.
633,952 professionals have used our research since 2012.