We recently added a new YQL execute method: y.pipe(pipeid,params)
pipeid (required string)
params (optional json object)
A response object that contains a result instance or an error object
Why would you want to do this?
1. Allows you to utilize all the benefits that a YQL execute statement gives you.
2. Higher rate limits! Benefit from YQL rate limits instead of Pipes (which is much lower).
3. Mash ups with other YQL tables
This is the Pipe that I want to run in YQL: http://pipes.yahoo.com/pipes/pipe.info?_id=990bf4c00040ad06ba83de9aadd6293b
Here is a simple sample YQL table that uses y.pipe. You can create one too using the YQL Table Editor.
And this is the YQL Query I would run to access my example: use “store://HuTaxj5021R7THBitCNIcJ” as ypipe_example; select * from ypipe_example
(You could always extend the sample table to accept the pipeid or pipe params as a parameter via the input keys)
Currently YQL does not produce the output formats that Pipes does (RSS, KML, ICAL, CSV).
YQL will only currently produce XML, JSON, JSONP and JSONP-X output formats.