Application Programming Interfaces (APIs) are a collection of endpoints, organized into different stages. They play an integral role in the deployment of a workflow, providing organization and security capabilities with the help of api-specific keys. A single API can have multiple stages (parallel versions) working exactly the same way but running in different environments. Endpoints, however, are strings that correspond to the URLs which you must access so that the API can be triggered for a particular stage or called from other systems.
Each API and stage can have different endpoints, with basic HTTP methods supported. You will have copies of all endpoints in each stage that you build. The same endpoint sometimes map to a different set of workflows that are powering that endpoint. As a result, APIs are key to maintaining a unique API Gateway system designed to provide external and internal access to the VMware BMA environment. This allow users to contribute to the backend part of web applications without even having to know how to program. It’s the power to create small services and publish them to other teams as building blocks of what they want to achieve.
A direct result of deployment is the generation of a universal and unique flow URL. Users can change the name of the workflow later and still use the same URL to access it. Unlike regular workflows, deployed workflows are considered active and are counted towards your license. You can check relevant limitations for your account in About VMware. This tab stores and manages the APIs you create and use for the deployment of your workflows.
