Our primary use case is API connectivity when integrating different systems or applications with the help of the API. There is a very robust API architecture that helps in directing different applications. In the B2B space, they have come up with a new offering, which is a partner manager, that helps to have the B2B integration with any EDI, X12, or any other B2B transactions. 

We worked predominantly for the BFSI financial sectors and for one of the automobile industries. They're taught in Europe. 

The applications where the customers wanted to download a report, a customer is associated with multiple customers, where they wanted to download the reports for analytics or just wanted to see what is the annual income or something like that. We expose an API for each customer. We will apply a policy where the APIs are being secured. So, each customer will have their own client ID and client secrets.

Our primary use case for this solution is for infestation and backend services. It is also a gateway. We use it heavily because Azure offers better pricing than its competitors. 

In addition, we use MuleSoft to run APIs. 

Our primary use case for the solution is managing all the new APIs, and we deploy the solution on cloud.

I work for customers in the retail and estate industries. We primarily use the solution to automate HR-related business processes. It includes interactions with the customers, making dashboards for customers, product to cash, and some other actions.

We primarily use the solution for API management.

We use MuleSoft API Manager effectively to manage traffic, especially in scenarios where we need to control access to sensitive data for public bodies. By implementing the API gateway, we ensure traffic control and enhance security for personal data APIs. This solution provides a layer of control and security without changing our existing technology stack. It also helps in managing traffic for mobile applications, ensuring seamless consumption of our services while applying necessary policies for governance.

API Led Composable Architecture and Batch Integrations to deal with big volumes

We primarily use the solution for API management.

We could employ it for tasks like access control and other minor functions like controlling licenses using an API gateway alongside SS rules.

We are using the solution to move away from a point-to-point integration to a more managed API platform while doing analytics to monetize the API. We use the solution daily.

We primarily use the solution for integration purposes. 

We primarily use the solution for our APIs. We are moving from monoliths to API architecture and we have approximately 10,000 to 12,000 APIs across banks, which are hosted on this product. It also provides us a gateway service to ingress the traffic as well as whole policy management where stuff is taken care of from the PC Any Point. It also has some API-level runtime policy management, which we use.

I use Mulesoft Anypoint API Manager for application integration.

We use it for integration with backend applications. We use it to connect to applications like SAP databases, or Infomatica Collibra or MongoDB, and some other backend applications.

I have dealt with a few use cases involving MuleSoft Anypoint API Manager, but I am unsure whether its features are useful in my company. The tool is useful for the governance of APIs that I have created with some policies, like SLA-based policies or rate-limiting policies. In general, it is an advanced product.

The main reason for using MuleSoft Anypoint API Manager is that the company's external systems inside the customers' ecosystem need to be publicly called APIs by providing the paid version of API so that anyone can access the endpoints from the internet. In our company, we need some tools to configure who can or can't call you while being able to control the amount of calls, irrespective of how many they are. In our company, the tool becomes useful to make five calls per minute with our current license.

The use cases are regarding telecommunication provisioning. Another aspect involves managing logistics, which includes connecting suppliers and the company's partners.

We do business with a lot of other vendors and customers. Our main core business is to lend loans and lease furniture. In this context, we have to create partners and we have to do multiple transactions with multiple vendors and multiple facilitators. In this venture, we consider APIs the best, and our most sophisticated medium to communicate with other partners and other lenders at home and elsewhere.

We want APIs to be the most sophisticated and more robust. REST APIs are the core in this area. We have been using Mulesoft specifically to create our REST APIs, enlarge them, and also expose the endpoints to our vendors so that they can use them. Internally, we have been using the APIs extensively for all of our internal application communication. Raw ping and workflow and all those things. We use this Mulesoft extensively for API management, REST API stack, and also for the workflow.

We utilized Mulesoft API Management for a learning management system and content management system for the education sector.

We used the latest version of this solution. It was deployed on a hybrid Azure cloud.

There are around 200 people using this solution.

We are solution integrators and this is one of the products that we implement for our clients.

It is used for integrating and logging data from legacy systems to make it available for other systems within the IT infrastructure in the enterprise. It is also used for data migration and making it available for customers, devices, services, and so on.

Essentially, it is for data governance and API governance.

We use the product to integrate and orchestrate data and manage APIs across multiple services.

I am offering consulting services to help clients build the API. I am not involved in the deployment or anything behind the API.

We are using the Anypoint component for the integration layer which is not specific to the API management.

Our first primary use case for this solution are APIs based in MuleSoft. It's natural to use the MuleSoft API manager for MuleSoft APIs. We also use this solution's API manager to manage non-MuleSoft APIs in environments based on the MuleSoft platform. It functions as a kind of API gateway for us.

This solution was primarily used for data retrieval.

I am an enterprise architect.  I work with Anypoint API Manager and MQ as part of my role in MuleSoft projects.

Typically, the customers use it to capture events from Salesforce in the auto industry, sending these events to their backend systems. They mainly process events from Salesforce.

I use MuleSoft Anypoint API Manager to manage and work on APIs for my company.

I mainly use Anypoint for data integration and flow, and securing, transferring, and monitoring data logs.

We use the solution to integrate various applications and services, whether it's integrating Salesforce or other third-party systems.

We use the product to integrate different systems in our organization. 

I have used this solution for an Europe based customer. They have ticketing tools like ServiceNow and other applications in their multiple locations including Asia, the Pacific and North America. The idea was to integrate data communication between those applications.

We use Mulesoft Anypoint API Manager for different reasons, it depends from project to project. We mainly use Mulesoft Anypoint API Manager to orchestrate some internal system integration processes.

Functional:  Integrate Supply Chain automation; Financial System integrations

Technical: Expose API's to Trading Partners

We use MuleSoft Anypoint API Manager across our integration team to move existing integrations and implement APIs. We are system integrators and I'm vice president of the company.

The solution is basically a SOAP API and REST API.

My primary use case for the solution is as an API gateway. I am an enterprise integration consultant and I implement it for customers.

I deploy this solution for my clients. 

The primary use case is for partners to exchange data and information with our company. It can be board members, as well as customers that can connect with us in order to exchange data. 

We are a solution provider and this is one of the products that we implement for our clients.

Mulesoft Anypoint API Manager has many use cases that involve API integration.

I have API experience with the entire lifecycle using Mulesoft.

This solution is widely used in API integration and there are many different use cases for it.

Our primary use is the interconnectivity of exposed APIs. The transformation layer is huge on the MuleSoft platform.

My primary use case is investigating the pros and cons of different platforms for the benefit of the application lifecycle. This includes security and other aspects. One of my goals is to make it easier to create API inventories.

Our primary use case is for connecting IT systems between each other. Because there are so many interconnections. It makes the connection easy to manage and simplify.