Technical Name | The technical name of an API must be unique. |
---|---|
Display Name | The display name can differ from the technical name and does not have to be unique. |
Description | The description of the API is displayed in the Developer Portal. |
Status | A disabled API can no longer be subscribed to and is no longer visible in the Developer Portal. |
Image | The image of the API. It is also displayed in the Developer Portal. |
Organization | The organization of the API. Who is allowed to see it also depends on this. |
Tags | With the tags you can categorize APIs. e.g. you can search for the tags in the API overview. |
Platform | If the API was discovered by an environment, e.g. AWS, it is assigned the type AWS and is therefore a "Native API" in this case from the AWS platform.
|
Git | Set up a repository to version your API and deploy it to other environments |
An API must be part of a product in order to be subscribed.
Create a new API from Specification File
To get started, simply open your API Control Plane instance and follow the instructions as described in https://apiida.atlassian.net/l/cp/mk7so1AQ .