Sending HTTP Response that swagger understands

Good Afternoon!   I am working on some REST services that uses a fairly extensive microflow that could return a variety of errors. I am wondering if there is a certain structure of HTTP response that is understood by swagger documentation? Right now my response status codes are returning correctly when I test the calls but swagger is not documenting the different responses and their status codes up front.  I have tried to find documentation that describes this but I am currently out of luck. If anyone has any information or documentation to refer me to so swagger will automatically document the different response status codes that would be much appreciated! Edit: Adding some extra information, I am currently returning an HTTP response object at the end of my microflow and using an export mapping to convert a list into a json and including that in the content of the HTTP reponse object.
0 answers