RedShipRedShip| DOCUMENTATIONDashboard

RSS and JSON feeds

The no-code way in. Your feed URLs are on Alerts dashboard → Delivery.

https://redship.io/feeds/alerts/<token>.xml    # RSS 2.0
https://redship.io/feeds/alerts/<token>.json   # JSON Feed 1.1
  • The last 100 delivered alerts, newest first. Capped matches are not in the feed.
  • Add ?keyword_id=<id> for a feed of one keyword (ids from GET /api/v1/keywords).
  • Cached for 5 minutes. Readers polling every 15 to 60 minutes see everything.
  • The <guid> (RSS) and id (JSON) is the alert's inbox_id, so readers deduplicate correctly.

Where it works

| Reader | How | | --- | --- | | Slack | /feed subscribe https://redship.io/feeds/alerts/<token>.xml in any channel | | Zapier, Make, n8n | "RSS by Zapier" or the RSS trigger node | | Feedly, Inoreader, NetNewsWire | Add the .xml or .json URL |

JSON Feed extras

Each JSON item carries the full webhook payload under _redship, the custom-extension key the spec reserves, so a script reading the feed has keyword_id, subreddit, upvotes… without calling the API.

{
"id": "c0a8…",
"url": "https://www.reddit.com/r/productivity/comments/…",
"title": "[r/productivity] Looking for a Notion alternative for a small team",
"content_text": "We are five people and Notion got slow…",
"date_published": "2026-08-26T09:41:12+00:00",
"tags": ["notion alternative", "r/productivity"],
"_redship": { "event": "post", "keyword_id": "5b2c…", "upvotes": 3, … }
}

The token

The feed token is not your API key. It is a separate secret, because a feed reader stores its URL in clear. Regenerate it from the Delivery page whenever you want: the old URLs stop working at once.