As long as the $content is mapped, everything else you pass in the mapper goes to the header.
This is the only thing I have in the pipeline.
You should read the Ultra Documentation again specifically concentrating on these points.
The unlinked output view type can be binary or document as well:
If it’s document, the output should have a ‘content’ field that will be JSON-encoded and sent back to the client. The other fields in the output document will be treated as HTTP response headers to send back to the client. If there is no ‘content’ field, the entire document will be JSON-encoded and used as the response body to be sent back to the client.
If the output document contains a ‘status’ field that is an integer, it will be treated as the HTTP response status code.
If it’s binary, the binary document’s header will be sent back to the client as the HTTP response headers. The body of the binary document will be directly streamed back to the client.
SnapLogic expects exactly one output document for every input. If no output is sent, then the original HTTP request sent to the FeedMaster will hang and eventually timeout. If more than one output document is generated, then SnapLogic will only send the first one back as the response to the original HTTP request. This behavior is different from a Triggered Task, where all of the documents sent to the unlinked output are sent back in the response.