Skip to Content
Last modified by Danniar Firdausy on 2024/09/30 17:12
From version 35.56
edited by Danniar Firdausy
on 2024/09/27 16:00
Change comment: There is no comment for this version
To version 35.60
edited by Danniar Firdausy
on 2024/09/27 16:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -75,10 +75,14 @@
75 75  
76 76  Quite similar with the "Parameters" tab, in the "Request" tab of the API Catalog page, you can also specify the description and whether the request body is required in the request. The screenshot below shows how the Request "Description" is reflected in the Swagger UI.
77 77  
78 -[[image:Main.Images.Microlearning.WebHome@intermediate-api-management-updating-your-api-gateway-operations--request-description.png]]
78 +[[image:Main.Images.Microlearning.WebHome@intermediate-api-management-updating-your-api-gateway-operations--responses-description.png]]
79 79  
80 80  ==== 3.3.4 Edit Responses ====
81 81  
82 +Lastly, the "Responses" tab of the API Catalog page also allows you to specify the response description and example response (along with its "Media type") for a specific HTTP status code. The screenshot below shows what are listed in the "Responses" tab is reflected in the Swagger UI.
83 +
84 +[[image:Main.Images.Microlearning.WebHome@intermediate-api-management-updating-your-api-gateway-operations--request-description.png]]
85 +
82 82  As is the case with all new versions in Create, the changes will only be effective when you deploy your solution via the eMagiz Deploy phase.
83 83  
84 84  {{info}}To ensure that the changes to your Swagger file generated by eMagiz are shown to the end-user, the latest version of the API Gateway runtime infra flow needs to be included in the release and deployed to the correct environment.{{/info}}