I can't judge the economic impact of that for you. But with a service like this, it's just so easy to do that you might want to prioritize it :) If your model i

I can't judge the economic impact of that for you. But with a service like this, it's just so easy to do that you might want to prioritize it :) If your model is pull based, you create a second endpoint that puts the data you'd normally output directly (otionally minus the JSON dressing) into the content field of RSS items. If it's push based, you could even write into an XML file on your server somewhere and let users access that. In the end, RSS is just some XML dressing around your data, and can be as easily implemented as a html template. Storing your old data (a RSS feed should not contain only one item) might be the biggest hurdle, if you don't do that already. Or you just send your users to Pipes, they could use a download and "build feed" block to create a feed on their own ;) Edit: Though I noticed that the endpoint of your loops can be specific actions, like a text message, that wouldn't translate of course. More a "put it into the feed" target action then.