In Choreo Connect 1.1.0 release, mock APIs are supported considering the API definition file. Users can define mock responses in Open API Specification 3 (OAS 3) or using Swagger definition. With the latest WSO2 API Manager 4.1.0 release, the relevant endpoint type for this API type is Mock Implementation Endpoint type. These APIs are manipulated under the pre-released API lifecycle state. With Choreo Connect API definition based mock implementations, you can define default responses, HTTP status code based responses, status code based preferred response retrievals. Unsupported mock API requests are handled by Choreo Connect returning a predefined response message. Also you can retrieve the responses by specifying the content type that you want to retrieve. You need to specify supported content types in the API definition in order to retrieve the response by the content type. In WSO2 API manager 4.1.0, mock APIs are allowed to invoke considering API subscriptions. Finally by using the Choreo Connect analytics data passing capability, you can pass analytics data to the Choreo insights. It facilitates to view mock API invocations considering different aspects.

API definition used in the tutorial: https://youtu.be/5cY4gPj2h7w