Supported HTTP Methods
...
Pipeline Design for GET Requests
Triggered Tasks support viewing the output of a Pipeline. When you execute a Pipeline using a Triggered Task URL, the output can be included as response to the HTTP request. You can create a Pipeline to be used in this manner by leaving one output view unconnected. For example, a Pipeline that consists solely of a File Reader Snap would return the contents of the file when the Task URL is requested.
This feature works with both document and binary views.
- Document view: the response consists of a JSON-encoded array of each document read from the view. If the output document contains a Status field that is an integer, it is treated as the HTTP response status code.
- Binary stream: the binary data's header is sent back to the client as the HTTP response header. The body of the binary data is directly streamed back to the client. You can use a formatter Snap, like the XML or CSV Formatter Snaps, to transform the output of a document view into a binary view if the default JSON-encoding does not work.
Pipeline Design for POST Requests
...