Deploying APIs¶

The private APIs can be used within the OU after being released on EnOS, while the third-party APIs can be invoked by a third-party only after being released and set as public on EnOS.

This section shows how to deploy APIs.

Before You Start¶

Ensure that you have an EnOS account and the permissions to create APIs in the EnOS Management Console. For more information, see Policies, Roles, and Permissions.
Ensure that you have completed the Creating APIs task.

Procedure¶

Log in to the EnOS Management Console and select API Management > My APIs.
Click the API group where the API to be deployed is located.
In the API List:
- For both private APIs and third-party APIs, switch the Status from Offline to Released by clicking on the Release icon.
- For third-party APIs, switch the Status from Offline to Released by clicking on the Release icon. You can test the API that is going to be public. For more information about testing the API, see Testing APIs.
- For multiple private APIs, you can select them in the API List, and click Batch Release to change their Status from Offline to Released.
For the released and tested third-party API, switch its Visibility from Private to Public to complete its deployment.
- For multiple third-party APIs, you can select them in the API List, and click Batch Public to change their Visibility from Private to Public.

Results¶

The private APIs with a status of Released can be used in the OU.
The third-party APIs with a Public Visibility will be listed in API Management > Public APIs.

Next Step¶

You can delete those APIs that are no longer needed. See Deleting APIs for more details.