FeedPress Support

Appearance

Creating a private feed ​

Private feeds in FeedPress allow you to control access to your RSS feed using private keys. This is perfect for premium content, paid subscriptions, member-only newsletters, private podcasts, or internal company communications.

What is a private feed? ​

A private feed in FeedPress is an RSS feed that requires a private key to access. Instead of being publicly available, viewers must use a special URL with a private key parameter to subscribe to and view your content. Each private key can be configured with usage limits and can be tracked for analytics.

Prerequisites ​

Before you can create a private feed, you must have a custom hostname configured for your feed. This is required for security and ensures your private feed URLs are served from your own domain.

Setting up a custom hostname ​

  1. Go to your FeedPress dashboard and navigate to Hostnames
  2. Create a new custom hostname (e.g., feeds.yourdomain.com)
  3. Configure DNS to point your hostname to FeedPress servers
  4. Add your feed as a custom hostname record

Setting up a private feed ​

Step 1: Enable private feed feature ​

Once you have a custom hostname configured:

  1. Go to your feed dashboard and select the feed you want to make private
  2. Navigate to Private Keys in the Extras menu
  3. You'll see a section to enable the private feed feature
  4. Click Enable Private Feed Feature
  5. Confirm the action - this will make your feed private and require keys for access

Step 2: Create private keys ​

After enabling the private feed feature, you can create private keys:

  1. In the Private Keys section, scroll down to "Create a new private key"

  2. Fill in the key details:

    • Key name: A descriptive name for this key (e.g., "Premium Subscribers", "Beta Testers")
    • Key value: Leave blank to auto-generate, or provide your own
    • Signatures limit: Maximum number of unique devices/browsers that can use this key (default: 300)

  3. Click Create a new key

Step 3: Distribute private feed URLs ​

Each private key generates a unique URL that subscribers can use:

https://your-custom-hostname.com/feed?key=YOUR_PRIVATE_KEY

For example:

https://feeds.yourdomain.com/feed?key=abc123def456

How private keys work ​

FeedPress private feeds use a signature-based system to limit access:

  1. Signatures: Each unique device/browser combination creates a "signature" based on IP address and user agent
  2. Limit tracking: Each private key tracks how many different signatures have accessed the feed in the last 30 days
  3. Access control: Once the signature limit is reached, new devices are denied access
  4. Automatic cleanup: Signatures older than 30 days are automatically removed from the count

This system allows for:

  • Controlled sharing while preventing unlimited distribution
  • Automatic handling of device changes and updates
  • Flexible limits based on your subscription needs

Managing private keys ​

Viewing existing keys ​

In the Private Keys section (found under the Extras menu), you can see all your created keys with:

  • Key name: The descriptive name you gave the key
  • Key value: The actual private key string
  • Signatures: Number of unique devices currently using this key
  • Limit: Maximum allowed signatures for this key

Key management actions ​

For each private key, you can:

  • Delete: Permanently remove a key and revoke all access
  • Reset: Clear all signatures, allowing the key to be used by new devices up to the limit
  • Increase: Raise the signature limit if you need to allow more devices

Best practices for key management ​

  • Use descriptive names: Make it easy to identify what each key is for
  • Set appropriate limits: Consider how many devices your subscribers might use
  • Monitor usage: Regularly check signature counts to understand usage patterns
  • Reset when needed: Clear signatures for keys that have reached their limit but need to accommodate new devices

Adding a private feed to RSS readers ​

Since private feeds use URL parameters rather than authentication, they work with any RSS reader:

Any RSS reader ​

  1. Copy the complete private feed URL (including the ?key= parameter)
  2. Add it as a new feed subscription
  3. The feed will work immediately without additional authentication prompts

Example URLs: ​

# Standard private feed URL
https://feeds.yourdomain.com/feed?key=abc123def456

# API access (for developers)
https://app.feedpress.com/api/feeds/yourfeed?key=abc123def456

Troubleshooting private feeds ​

Common issues ​

"Invalid key" error

  • Verify the key is correctly copied (including the full key value)
  • Check that the key hasn't been deleted
  • Ensure you're using the correct feed URL

"Too many different private feed accesses" error

  • The key has reached its signature limit
  • Use the "Reset" action to clear old signatures
  • Or "Increase" the limit to allow more devices

Feed not updating

  • Private feeds update on the same schedule as public feeds
  • Check that your source feed is publishing new content
  • Verify the private feed URL is working in a web browser

Testing your private feed ​

  1. Copy the private feed URL from your FeedPress dashboard
  2. Open it in a web browser - you should see the RSS XML content
  3. Test with different devices/browsers to verify signature tracking
  4. Try the URL in your preferred RSS reader

API access for private feeds ​

Private feeds also work with the FeedPress API:

GET https://app.feedpress.com/api/feeds/yourfeed?key=YOUR_PRIVATE_KEY

This is useful for:

  • Custom applications that consume your private feed
  • Automated systems that need feed access
  • Integration with third-party services

Analytics and monitoring ​

Private feed access is tracked in your FeedPress analytics:

  • Hit tracking: Each private feed access is counted in your statistics
  • Key usage: Monitor which keys are being used most
  • Signature tracking: See how many unique devices are accessing each key
  • Geographic data: View where your private feed subscribers are located

Security considerations ​

  • HTTPS only: Private feeds should always use HTTPS URLs for security
  • Key rotation: Consider creating new keys periodically and retiring old ones
  • Limit monitoring: Regularly check signature counts to detect unusual usage
  • Custom hostname: Using your own domain adds credibility and control

Use cases for private feeds ​

Premium content subscriptions ​

  • Create different keys for different subscription tiers
  • Set signature limits based on subscriber plans
  • Monitor usage to understand subscriber engagement

Internal company feeds ​

  • Distribute company news or updates securely
  • Limit access to specific teams or departments
  • Track engagement across different groups

Beta testing and previews ​

  • Share upcoming content with select audiences
  • Limit distribution to prevent leaks
  • Gather feedback from controlled groups

Podcast monetization ​

  • Offer ad-free or bonus content to paying subscribers
  • Create exclusive episodes for different tiers
  • Track subscriber engagement and retention

Private feeds provide a powerful way to monetize content, create exclusive communities, or share sensitive information securely while maintaining full control over access and distribution.