I am currently working on Axway AMPLIFY API Management, which is the Axway API platform. The main requirement for API management is that the API platform provides security to the different APIs which fetch data from the front end and back end. If a customer needs to fetch data from the back end, which could be any database or any organization that has the data, that customer goes through the API platform. Axway AMPLIFY API Management maintains security throughout the entire process. Whatever checks, credentials, API keys, authorization, or authentication is required by the database to confirm that the customer is valid is performed by the API platform.

The integration part of Axway AMPLIFY API Management works as a middleware platform and helps with integration with different parties on both ends. Think of it as an hourglass funnel where many different APIs sit at the top and slowly move downwards through that funnel. At the center is an API Gateway platform which checks every API, verifies all the security, processes all integration features, and sends the data downwards. From an integration point of view, the parties sitting at the top could be Mulesoft, Boomi, Dynamics 365, or any other specific tool that is integrated. The call goes from these tools to Axway and then to different vendors, which could be any third party or out-of-organization teams. Alternatively, data could come from outside the organization into the Axway system and then be sent to Dell, Boomi, or Mulesoft integration tools. Axway AMPLIFY API Management is capable of handling the integration in both directions, meaning both parties must integrate the specific API URL to reach the back end or front end.

Our main use case for Axway AMPLIFY API Management is to use the product as an API gateway for securely exposing and accepting calls from the internet, such as securely exposing the web APIs or REST APIs developed within the network, and having authentication layers around it. This is a primary use case, and we also leverage the portal part of the product so that developers can come in, explore our APIs, and if they find that it is of use for them, then they can register and start doing business with us.

The integration features of Axway AMPLIFY API Management are very useful for us, as I am employed as one of the leading internet providers in the UK, where I work as a platform manager. It is very important for us and our external consumers, communication partners such as Vodafone, TalkTalk, and Sky, who wish to use the functionality of the APIs that we are exposing. Integration is very helpful for us by helping expose the APIs as REST APIs.

We use the solution for ESB and B2B integration between the systems of our business.

There are APIs, which we call application programming interfaces, in IT. These are the calls, which generally take the data from one place and send it to the other. Their mode of operation is simply transferring the data from one place to the other. APIs are handled by their own gateways and their own management. Axway AMPLIFY API Manager is a tool used to manage API calls. Because they contain sensitive data, security is important and is applied through the use of APIs. The API Manager is an interactive tool that allows applications to communicate with each other. The solution also facilitates data transfer, which can be secured through the use of APIs.

The solution can be deployed both on-prem and the cloud, but 99 percent of the customers for which I have worked, deploy on the cloud. Both AWS and Azure but most of the time the solution is deployed on AWS.

We use Axway for exposed APIs and REST APIs, basically. We also use it internally and expose it for external consumption, essentially.

We use Axway Amplify API Management for primarily two use cases. The first one involves an API Gateway exposed on the DNC layer to allow external organizations to connect to internal APIs. The second use case is when applications within the organization need to connect to already hosted APIs, which is done through an internal gateway. These two use cases are supported by APIs built around them.

We use this solution for our e-commerce clients. 

We make use of Axway's API gateway API management tool.

Its integration with middle wear is similar to ESB. We provide integrations as we are a swift services bureau. We've got customers that are banks and in some use cases. We integrate these banks with their own back office and we tend to provide integration for that. 

We also make use of the solution to build a marketplace of financial services, which is basically our own solution. 

For other customers, we do integration of the various source systems, back-office systems, legacy systems, etc. We also do file transformation where we take messages for customers in their environments and translate it to industry formats. 

We have a service running on Xray Cloud and we have established an internal API gateway platform. It is used for customer-centric APIs.

We use Axway AMPLIFY API Management for bank payments and bank transactions.

We use it as a transport mechanism. 

We use this solution to offer API for our on-premises environment applications, as well as API from a cloud perspective. We have a hybrid-cloud deployment model.

This is a SaaS platform and it is running permanently.

Our primary use for this product is to control how we expose APIs.

Our primary use for the solution is providing APIs to external parties through communication protocols.