Managing API Namespaces
Create an API Namespace
To create an API Namespace, use the Create capability in the API Namespaces Overview section or in the Navigation.
An API namespace is defined by the following master data:
Property | Description |
Prefix |
This is the prefix of the API namespace. It is unique within an API solution. Please note that only the characters A-z (without special characters), digits and the special character "_" are permitted for a prefix! Furthermore, prefixes may not begin with a digit and the first character must be lowercase. A prefix can not consist more than 6 characters. The prefix cannot be changed after creation. This field is mandatory. |
Label |
This is a meaningful title of the API namespace. This field is mandatory. |
Description |
This is the description of the API namespace and its lifecycle. This field is optional. |
Create API Namespace from Scratch
After selecting and confirming the “from scratch” option you have to provide the following metadata about the API.
Property | Description |
API Title |
Title of the API. This field is mandatory. |
API Description |
Description of the API. This field is optional. |
HOST |
Base URL for API calls. The host of the Server is only a placeholder and will be substituted depending to the deployment. The base path is prefilled with the prefix of the API Namespace This field is mandatory. |
Contact E-mail |
Contact E-mail of the API. A valid E-Mails must be provided. This field is optional. |
Contact name |
Contact name of the API. This field is optional. |
Contact URL |
Contact URL of the API. This field is optional. |
License Name |
License Name of the API. This field is optional. |
License URL |
License URL of the API. A valid URL must be provided This field is optional. |
Terms of service URL |
Terms of service URL of the API. A valid URL must be provided This field is optional. |
By proceeding with next you can select the format for the API Specification (OpenApi 3.0 or Swagger 2.0) you want to generate and add additional Integration Artefacts that should be automatically produced during the build process of the solution. Create after that will persist the new API Namespace.
Edit an API Namespace
To edit an API Namespace, navigate to the Namespace Details view of the API Namespace that is accessible by clicking on the namespace itself from the API Namespace overview page.Edit the Master Data
By navigating to the Master data section and by using the Edit master data capability, you can adjust the "Label” and "Description". You can confirm your entry by using the Save capability.
Edit API Information
By navigating to the API Information section and by using the Edit API Information capability, you can adjust the following information:
Property | Description |
API Title |
Title of the API. This field is mandatory. |
API Description |
Description of the API. This field is optional. |
Contact E-mail |
Contact E-mail of the API. A valid E-Mails must be provided. This field is optional. |
Contact name |
Contact name of the API. This field is optional. |
Contact URL |
Contact URL of the API. This field is optional. |
License URL |
License URL of the API. A valid URL must be provided This field is optional. |
Terms of service URL |
Terms of service URL of the API. A valid URL must be provided This field is optional. |
Edit Build Information
By navigating to the Build information section and by using the Edit Build Information capability, you can adjust the "Supported API Specification” and the additional API Integrations. You can confirm your entry by using the Save capability.
Delete an API Namespace
You can delete an API namespace by navigating to the details view by clicking on the namespace card and using the Delete capability.
You will need to confirm the action before the selected command is permanately deleted.