This documentation is for WSO2 API Manager 2.0.0 View documentation for the latest release.
Page Comparison - Extending the API Life Cycle (v.4 vs v.5) - API Manager 2.0.0 - WSO2 Documentation

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • Define your own life cycle states in the API life cycle 
  • Change the state transition events as per the environmental preferences
  • Add custom checklist items for specific state transitions
  • Change the execution code for each state transition


    For all state transitions, the same execution class is used (org.wso2.carbon.apimgt.impl.executors.APIExecutor).  However, you can plug your own execution code when modifying the life cycle configuration. For example, if you want to add notifications for a specific state transition, you can plug your own custom execution class for that particular state in the API life cycle. Any changes are updated in the Lifecycle tab accordingly.

 When When a new transition event is introduced to the life cycle, an entry must be made to the locale_default.json file in order to view that life cycle transition event in the Publisher Lifecycle tab. This is introduced to support multi-language facility. For example, let's say a transition event called Notify Users is introduced in the DEPRECATED state as follows,