The problem these tools have now
A monitoring tool is a promise: tell me when someone on Reddit says this. For years that promise was kept with a search RSS feed polled every few minutes, or with the public Data API walking /r/all/new. Reddit stops RSS on 13 Nov 2026 and closes the public Data API to unregistered apps on 12 Jan 2027 and to everyone in March 2027. A tool built on either goes dark on schedule, and its customers notice the same day.
Redlisten replaces the source rather than the product. The matching, the delivery and the dashboard you built stay; the posts and comments arrive from a service that is not subject to Reddit's shutdown dates.
Streams over every post and comment
A keyword stream is a saved search that never stops. Give it words to match in any, words that must all appear in all, words that disqualify a match in exclude, and optional community, author, language, score and content type filters. From then on every public post and comment that matches is added to the stream within seconds of being posted. Comments count. Most mentions of a product, a ticker or a competitor happen in comments, and a tool that watches titles alone reports a fraction of the conversation.
On paid plans a new stream fills with the last 30 days of matches when it is created, so a customer who sets up an alert sees history straight away rather than an empty screen. Pro keys hold 10 streams, Team keys 50 and Business keys an unlimited number, as listed on the pricing page on 6 Nov 2026.
# Create a stream and send every match to Slack and a webhook
curl -X POST "https://api.redlisten.com/v1/streams" \
-H "Authorization: Bearer rl_live_YOUR_KEY" -H "Content-Type: application/json" \
-d '{
"name": "crm shoppers",
"any": ["which crm", "crm recommendation", "replace hubspot"],
"exclude": ["hiring"],
"subreddits": ["smallbusiness", "sales", "startups"],
"types": ["post", "comment"]
}'
curl -X PATCH "https://api.redlisten.com/v1/streams/st_8f2k" \
-H "Authorization: Bearer rl_live_YOUR_KEY" -H "Content-Type: application/json" \
-d '{"delivery": {"slack_webhook": "https://hooks.slack.com/services/...",
"webhook_url": "https://yourapp.com/hooks/reddit",
"webhook_secret": "change-me"}}'Delivery that fits the product
Each stream carries its own delivery settings, changed with one PATCH. A webhook gets one POST per match with the full item, a permalink and an X-Redlisten-Signature header when you set a secret, with three retries and backoff. A Slack or Discord incoming webhook posts each match into a channel, batched when several arrive together. An email digest goes out daily or weekly. Polling with a cursor through /v1/streams/{id}/items is always available for tools that prefer to pull.
No code tools fit the same way. Zapier, n8n and Make all accept a webhook as a trigger, so a stream can start a Zap, an n8n workflow or a Make scenario per match, and that workflow can write to a sheet, open a ticket, enrich a lead or message a salesperson. For a tool whose customers configure their own alerts, the webhook URL is the whole integration.
Counts for the dashboard
Alerts are the loud half of monitoring. The quiet half is the chart: how many mentions a day, going up or down. /v1/streams/{id}/volume returns match counts by hour or by day for any stream, and /v1/trends answers the same question for any phrase without a stream. Team keys compare several terms in one call and rank the communities where a term appears most, which is the view a listening dashboard needs for a weekly report.
Usage and cost
Every call counts one request, and every post or comment returned counts as one result. There are no daily caps, so a tool can pull in bursts. A Pro key at $29 a month carries 50,000 requests and 1M results; a Team key at $99 carries 250,000 requests and 5M items; a Business key at $299 carries 1M requests and 10M results, with a live streaming connection and daily JSONL exports of each stream. Prices are as listed on 6 Nov 2026 and drop by two months when billed yearly.
A free key, issued at signup, holds one stream with email digests and 250 requests a month, which is enough to prove a match pipeline end to end before a customer is on it.
What to tell your customers
That the alerts keep working. The source changes under the hood, matches still arrive in seconds, comments are now included if they were not before, and search goes back 30 days. The search page covers the query syntax, the keyword alerts page walks through a no code setup, and the docs have every stream field.