< Back to Publish APIs

In the API lifecycle, after API creation and API registration follows API publishing. API Publishing refers to the process of making your APIs available to app developers for consumption. When the APIs have been successfully registered and tested, API developers first publish the APIs in a sandbox API environment. Then, when an API is ready to be consumed by other organizations, it is published in the API Catalog by the API owner. The API administrator must then approve the API as the final step to publish to other organizations in the API Catalog. When the API is published, the API administrator can authorize other organizations to access the API. API consumers who are members of the authorized organization are then able to see the API using API Publishing tools including the API Manager and API Portal. An API Manager is used to publish an API though an API Gateway so it can be secured and managed. The API Portal is used to publish an API and related documents to the API Developer Portal so that it can be consumed by either external or internal developers. When an API is published, only the API administrator can make changes. The published API can only be deprecated or unpublished, and cannot be deleted. A published API cannot be edited, and must first be unpublished. Unpublishing an API stops any client applications using the API. However, the API administrator can edit the API documentation of a published API. This allows changes in the API documentation without impacting the API availability.">API lifecycle, after API creation and API registration follow API publishing. API Publishing refers to the process of making your APIs available to app developers for consumption. 

When the APIs have been successfully registered and tested, API developers first publish the APIs in a sandbox API environment. Then, when an API is ready to be consumed by other organizations, it is published in the API Catalog by the API owner. The API administrator must then approve the API as the final step to publish to other organizations in the API Catalog

When the API is published, the API administrator can authorize other organizations to access the API. API consumers who are members of the authorized organization are then able to see the API using API Publishing tools including the API Manager and API Portal.

An API Manager is used to publish an API through an API Gateway so it can be secured and managed. The API Portal is used to publish an API and related documents to the API Developer Portal so that it can be consumed by either external or internal developers. 

When an API is published, only the API administrator can make changes. The published API can only be deprecated or unpublished, and cannot be deleted. A published API cannot be edited, and must first be unpublished. Unpublishing an API stops any client applications using the API. However, the API administrator can edit the API documentation of a published API. This allows changes in the API documentation without impacting the API availability.