[Back to Docs]

My Feeds Component


When we developed TweetBoost PRO we immediately imagined extending it’s scheduling powers to FaceBook, LinkedIn, and other custom destinations. We built our Feeds Component to help others, and ourselves, achieve this goal.

TweetBoost PRO users will find the feeds component is accessible from within wp-admin under the TweetBoost PRO  menu item with the sub-menu name ‘My Feeds’.

Our feeds include a list of Tweets that have have been published through TweetBoost PRO.  Feeds will not show Tweets scheduled into the future. This opens up your feeds to being used as too to post status updates to destinations beyond Twitter.

Account Feeds

We provide a feed for every connected Twitter account. We know that different accounts will have different content. Providing a feed for every account offers greater curation potential.

TweetBoostPRO provides 3 types of feeds for consumption.

  1. RSS Feeds
  2. XML Feeds
  3. JSON Feeds

RSS Feeds

RSS Feeds are powered by XML, so it’s a little strange to see RSS and XML included because it seems redundant, but there’s a reason why we have them both. Extra measure was added into RSS Feeds to make them as similar to content RSS feeds leveraged by CMS like WordPress, which are consumed inside services like Zapier and IFTTT

This is the format of a feed item you’ll find inside one of our generated RSS Feeds:

XML Feeds

XML Feeds are basically the same as RSS Feeds but you’ll notice this format contains more data elements than the RSS feed contains. We imagine this will be used in custom scripts more than it will be used with automation services like Zapier or IFTTT

JSON Feeds

JSON Feeds contain the same data found in XML fields yet we output the data in JSON format and use Tweet dates as object item keys. We are open to working with others on improving these feeds if needed.

We imagine JSON feeds will be used by developers working with custom publishing scripts. Here’s a quick example of a JSON feed with two items:


We can keep our feeds privately accessible by using a secret key. You can change this to anything you want as long as it’s URL friendly. This key will be required to access any one of your feeds.  If at any time you’d like to revoke a 3rd party from being able to read your feeds, just change your secret key from within the My Feeds access area.

Here’s an example of one of our feeds. Notice how we’re using our not-so-secret-key-12 inside the URL:


(It is possible we’ve changed our security key since writing this article and the above URL will not work. If it still works you’ll see a great example of our RSS Feed in action )


We’ll update this area soon with the tutorial we write to show you how we are leveraging these feeds, powerfully.