API Center includes the following changed behaviors in this release:
Managed API lifecycle
To simplify the usage of a managed API, the following changes are introduced in the managed API lifecycle:
•You can activate a deactivated managed API.
Previously, you couldn't activate and use a deactivated managed API.
•On successfully deactivating a managed API, the status of the managed API changes to Inactive.
Previously, the status was set to Deactivated.
•On the API Console page, you can use the Show Inactive APIs toggle button to see the list of deactivated APIs.
Previously, the toggle button was named as Show Deactivated APIs.
•If you have a Deployer role, you can edit a managed API when it is in the created or inactive state. You can't edit a managed API that is in the active, shared, or deprecated state.
Previously, with a Deployer role, you could edit an active managed API at any point during the managed API's lifecycle, regardless of its current state.
•When you create and activate a managed API, the state of the managed API remains in the created state if any operation within the API fails. The managed API state changes to the active state only when all of its operations are successfully published.
Previously, when you activated a managed API, if any operation within the managed API failed, the managed API's state changed to partially published. The partially published API state is no longer an available state value.
•When you create an OAuth 2.0 client, you can view all the managed APIs that are currently active, shared, and deprecated. When you edit an OAuth 2.0 client, you can view the list of active, shared, deprecated, and inactive managed APIs that are associated with the OAuth 2.0 client.
For more information about the managed API lifecycle, see Manage APIs.