Combining Feeds

Combining Feeds

RSS feeds are very powerful when it comes to aggregation and syndication. One of the main advantages of using a single format is that it becomes very simple to aggregate and combine several of them.

Let’s say we have identified 3 RSS feeds which we want to combine in a single feed and later display that combined feed on this page. The three feeds are this blog’s feed, our Tumblr feed (where we post RSS and open web related news) and our documentation’s commit log.


Even though our application will be executed in the browser, we need to make sure Superfeedr knows about these feeds and knows that we want to aggregate them. Let’s first create a subscriber account. Once the account has been created and confirmed (by email), we can log into Superfeedr and click on “Manage Susbcriptions”.

This page now lets us easily list, add or remove feeds (subscriptions). Since we have not subscribed to any feed yet, that list is empty. Click on the “New Subscription” button in the lower right corner. A modal opens and shows options when subscribing to a feed.

  • The hub.topic field is for the feed URL
  • The format field lets us pick between JSON or Atom. (we can pick either here because this only applies to notifications)
  • The 3rd item can be confusing. Since our browser side application will just pull the data from Superfeedr, we don’t need Superfeedr to push the data anywhere1 so we’ll just put which is Superfeedr’s Null Device.
  • We can leave the secret empty.

Once we clicked on Create, the modal should close and we should see the new subscription appear in the list of subscription. Rinse and repeat to add other feeds.

Retrieving the combined feed

Superfeedr’s API lets us retrieve each feed individually, using its url (as hub.topic) or several feeds matching the same criteria, using the hub.callback parameter. Here, we’ll use the latter.

However, before that, we need to create a token to authenticate our API call. In our Superfeedr dashboard, click on Authentication tokens. Pick a token name (be creative!) and select only the retrieve capability. This is important, because this token will be visibile to anyone who looks at the source code of the HTML page and we don’t want them to use the token to add new subscriptions. Once created, click on its name and copy the value from the modal.

Let’s now build the API request using Superfeedr’s PubSubHubbub Console. From the Dashboard, we click on Debug PuSH API requests. This console let’s us build and execute API requests. This is very convenient to get started. Let’s fill the field:

  • Step 1 let’s select the token we’ve just created in the first field
  • Step 2 asks to pick a hub.mode. We use retrieve.
  • Step 3 lets us set the parameters:
    • We leave hub.topic empty because we want to retrieve multiple subscriptions using their callback.
    • Let’s leave count to 5 items.
    • Select Atom for the format of the combined feed.
    • And put in the hub.callback field.
    • Leave all other fields unchanged (we removed them from the screenshot below for clarity).

You can visualize the full request, and click on Send Request to execute it from this console. You can also copy it to the clipboard if we’d like to run it in our Terminal application, rather than this javascription application. Since this is a GET request, we can also open the request in a new tab of the browser to see exactly what the feed looks like. (feel free to reuse this URL in any kind of feed reader!). For our specific example, this is the combined feed.

Displaying the feed in the browser

We now have a combined, aggregated feed. Let’s display it in the browser. We won’t be using any framework here, but feel free to check how superfeedr works with Jquery, Angular or React if you’re using any of these in your application already.

We’re string believer in the open web and when great open web protocols exist, we should use them. Here, EventSource is appropriate. We need to build the EventSource url:

  • We use the domain
  • we encode the hub.callback query string
  • we create an authorization query string parameter which is just a base64 encoded version of the login:token string. (you can also copy it from the URL when opening the combined feed in a new tab).

Here’s a code sample:

// First, we create the event source object, using the right URL.
var url = "";
url += "&hub.mode=retrieve";
url += "&";
url += "&authorization=c3VwZXJmZWVkcjpjNzU1ZjMyYjkzZmQ1MGM3NTQyZTIwNzYxOWJjMmI4NQ%3D%3D&";

We can then create the EventSource object:

var source = new EventSource(url);

// When the socket has been open, let's cleanup the UI.
source.onopen = function () {
  var node = document.getElementById('combined-feed');
  while (node.hasChildNodes()) {

// Superfeedr will trigger 'notification' events, for each entry in the feed
// We can just create a new DOM element for each item in in the combined feed.
// And add it to the UI
source.addEventListener("notification", function(e) {
  var notification = JSON.parse(;

  notification.items.forEach(function(i) {
    var li = document.createElement("li");
    li.innerHTML = '<a href="' + i.permalinkUrl + '"">' + i.title + '</a>';
    var node = document.getElementById('combined-feed');
    node.insertBefore(li, node.firstChild);

And here is the final result (it should also update in realtime, without refreshing the page if an item is added to any of the feeds):

  1. If we wanted Superfeed to ping a server side application (like a Ruby on Rails application or a Wordpress blog… or anything really, we’d put that application URL in there). 

Liked this post? Read the archive or

On the same topic, check superfeedr jquery, updated pricing and xmpp-ftw xmpp and json for the web.

Previously, on the Superfeedr blog: Searching Subscriptions.