In the overview you will see either a folder with APIs or a single API depending on what you have selected in Discover APIs . Therefore, other options will be available to you in some cases. In this case it is the Demo folder with three APIs.
Deployments
All gateways where your APIs are located are listed here.listed here for each deployment on each node. We also call these specific APIs running on a node an instance of the API. The "Scan for Deployments" button is used to scan the local clones of the nodes and update the list of instances. This happens automatically after each migration or reload of the resources.
...
APIs
If All APIs of the currently selected one is a folder, all APIs inside it will be displayed herefolder are listed here. In the top left of each tile, you will see the symbol for the API, the name of the API and the number of instances to the right. The metrics of all instances are displayed together below. Click to access the details of this API.
...
Migrations
Here you can migrate your APIs from git, from a gateway or even from a file to other gateways. You can also view the history of your past migrations
...
git Version Control
We recommend using git as the single point of truth of your APIs. How and why we show here: Here you can check the connection to the git repository and send the source code of the entire folder with all APIs and dependencies to and from git and also version it.
We understand the folders as a thematic unit of the APIs, so it is not possible to additionally connect the APIs within the folder with git.
...
Requirements
If your APIs require a solution kit or additional resources in the form of a library, you can note this here. During a migration, the system will then automatically check whether the resources and solution kits are available on the target.
...