What is your primary use case for Mulesoft Anypoint API Manager?

Our primary use case for MuleSoft API Manager is to manage APIs and publish APIs so that whoever is the consumer can understand and access the API specifications on the exchange. They can build their codes based on those specifications when calling or consuming our APIs or pushing data to our APIs. It is also used for testing purposes, as API Manager provides stubs for initial testing, which helps consumers.

Our company used MuleSoft API Manager when upgrading to a new SAP S/4 system. We created many APIs following the API-led architecture, building system APIs, processing APIs with our logic, and exposing these to other systems.

I use the solution in my company because we are looking at synchronizing all the messages that come into our trading platform. We are also looking at various applications and feeding points, and MuleSoft has been helpful for us. Essentially, the use case is attached to stock broking.

Our primary use case is to consolidate server information about product stocks. We have data in different systems and offer an API to provide users with consolidated information. Our main system is SAP, and we use standard connectors to integrate it with Microsoft.

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.

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.

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

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

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 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.

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.

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

We primarily use the solution for API management.

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

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.

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

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.

I use Mulesoft Anypoint API Manager for application integration.

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.

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.

I deploy this solution for my clients.

We primarily use the solution for API management.

The solution is basically a SOAP API and REST API.

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.

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.

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.

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

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.

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.

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 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.

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

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.

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.

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.