...
- CREATED: API metadata is added to the API Store, but it is not visible to subscribers yet, nor deployed to the API Gateway.
- PUBLISHED: API is visible in API Store, and eventually published (if the "Propagate Changes to API Gateway" option is selected at publishing time).
- DEPRECATED: API is still deployed into API Gateway (available at run-time to existing users) but not visible to subscribers. An API can automatically be deprecated when a new version is published.
- RETIRED: API is unpublished from the API gateway and deleted from the store.
- BLOCKED: Access is temporarily blocked. Run-time calls are blocked and the API is not shown in the API store anymore.
The API life cycle is exposed in the API publisher's end-user Web interface and is only visible to and manageable by a user who is assigned the "publisher" role. For instructions on creating a user with the "publisher" role, refer to section User Management.
...
1. Log in to WSO2 API Publisher as a user who has been assigned the "publisher" role. For example,
2. From the "All APIs" window that opens, click on the API you want to publish.
3. The API's information will be shown. For example,
4. Select the tab named "Life Cycle." Information on the APIs state will be shown as follows:
| Info | ||
|---|---|---|
| ||
The tab "Life Cycle" is only visible to users with "publisher" privileges. |
...
Three options will be available for selection as follows:
Propagate Changes to API Gateway
...
The API is now published and visible to consumers in the API Store. The API life cycle history will be visible at the bottom of the page as follows:
| Excerpt | ||
|---|---|---|
| ||
API life cycle management in WSO2 API Manager |
...