Syndicate perks as RSS
Expose your perks as a standard RSS feed that email platforms, CMSs, and automation tools can pull in — no API key, no custom integration.
Lots of marketing tools already know how to read RSS: newsletter builders that turn a feed into an email block, CMSs that render a feed as a section, automation platforms that trigger on new items. Instead of building a bespoke integration for each one, point them at your perks feed. The feed is public and updates as your collection changes, so those tools stay current on their own.
How it works
The feed is served per perks-page domain — the same hosted address your
customers visit — at a /rss path. It returns your collection's general
perks as RSS XML. General perks are your standing marketplace perks; the feed
deliberately leaves out single-use coupon perks and location- or time-specific
perks, which don't make sense as evergreen feed items.
Because it's meant to be consumed by third-party tools, the feed needs no API key — it's a plain public URL.
Before you begin
- Your perks-page domain. The hosted address for your perks page, e.g.
example-rewards.perkspulse.com. If you don't know it, see Use a hosted perks page for how to resolve it from your slug.
Steps
1. Build the feed URL
Append /rss to your perks-page domain:
https://perk-collections.paylode.com/perk-collections/example-rewards.perkspulse.com/rss
2. Fetch it
curl https://perk-collections.paylode.com/perk-collections/example-rewards.perkspulse.com/rss
The response is application/rss+xml — standard RSS with one <item> per
general perk:
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
<channel>
<title>Example Rewards</title>
<item>
<title>Get 16 free meals</title>
<description>up to 70% off — meals delivered to your door.</description>
<link>https://link.paylode.com/?upid=sample-opaque-ref</link>
</item>
</channel>
</rss>
Each item's <link> is the perk's Redeem URL — use it as-is.
3. Point your tool at it
Add the feed URL wherever your tool takes an RSS source — the newsletter's "RSS-to-email" block, the CMS feed importer, the automation trigger. The tool polls the feed on its own schedule and picks up changes.
Once you're live
As you add or remove general perks in the Paylode app, the feed reflects it on the next fetch. Downstream tools update whenever they next poll.
Troubleshooting
The feed carries general perks only. Single-use coupon perks and location/time-specific perks are intentionally excluded — if a perk you expect isn't in the feed, check whether it's one of those types. To render every perk type yourself, see Build a custom perk page.
The path segment is your perks-page domain, not your collection id. A wrong
or unrecognized domain returns 400 COLLECTION_NOT_FOUND.
Reference
This guide uses the public getPerkCollectionRss operation. See it in the
API Reference.
Related
- Perk Pages overview — what the product does and how this page fits it.