Home/Use cases/Trust and safety

Trust and safety

Risk shows up in comments before it shows up in headlines. Watch communities and authors across every public post and comment, get removals flagged, and route what matters to the people who act on it.

The gap in title level monitoring

Most monitoring reads titles. Fraud, harassment and impersonation live in replies: the comment offering a refund by direct message, the thread where a support account is being imitated, the user who shows up in five communities with the same pitch. A trust and safety team that sees titles alone sees the aftermath. Redlisten covers every public comment as well as every post, so the watch starts at the reply.

The source matters for continuity, too. Tools built on Reddit RSS lose it on 13 Nov 2026, and tools built on the public Data API lose that in March 2027. Redlisten is a separate service and those dates do not apply to it.

Watch a community

A keyword stream over a set of communities collects every post and comment that matches a pattern from the moment it is created. any lists the phrases that signal risk, all lists what must also appear, and exclude drops the noise. Author, language and score filters narrow further. A stream over your brand's own communities with a list of payment and contact phrases is the standard impersonation watch; one over a handful of high risk communities with a list of names or domains is the standard abuse watch.

# A stream over scam patterns in three communities, posts and comments, sent to 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": "gift card scams",
    "any": ["gift card", "steam card", "wire transfer", "cash app"],
    "all": ["dm me"],
    "subreddits": ["yourbrand", "yourbrandsupport", "scams"],
    "types": ["post", "comment"]
  }'

# Follow an author across the site, newest at the top, status included
curl "https://api.redlisten.com/v1/authors/example_user/comments?limit=100" \
  -H "Authorization: Bearer rl_live_YOUR_KEY"

# Check whether a post you flagged has since been removed
curl "https://api.redlisten.com/v1/posts/1xju19t" -H "Authorization: Bearer rl_live_YOUR_KEY"
# ... "status": "removed", "status_changed_at": "2026-11-05T14:02:11Z", "removed_by": "moderator" ...

Delivery goes where the team works. A Slack or Discord incoming webhook posts each match into a triage channel. A webhook POST per match, signed with a secret you set, feeds a case system or a Python service that scores the item and decides what to escalate. A daily email digest covers the low urgency watches. Streams are a paid plan feature, with 10 on Pro, 50 on Team and an unlimited number on Business, as listed on 6 Nov 2026.

Follow an author

When a pattern points at an account, /user/{name} and the native /v1/authors/{name}/posts and /v1/authors/{name}/comments return that account's activity across every public community, newest at the top. Each record carries the community, the text, the score and the stable account id, which survives a username change. A stream with an authors filter keeps watching from then on and alerts the moment the account posts again, anywhere.

Removals, flagged

A post or comment that is removed by moderators or by Reddit, or deleted by its author, is delivered again on the native feeds with status set to removed or deleted, a status_changed_at time, and removed_by where it is known. The captured text stays in the record. For a safety team that means the evidence survives the takedown, and the takedown itself is a signal: a burst of removals in a community is often the earliest sign of a coordinated problem. Scores and comment counts keep refreshing as a thread grows, so the same record also shows whether a thread is spreading.

Reddit style paths show [removed] and [deleted] in place of the text, as Reddit does. Use the /v1 endpoints when the content itself is needed for a case.

Thread context in one call

A flagged comment is rarely enough on its own. /comments/{id} returns the post and its full comment tree with parent_id and depth on each comment, so the reviewer sees who said what to whom. Full text /search over the last 30 days answers the follow up questions: has this phone number appeared before, which communities, which accounts. Search covers comments, and author: and subreddit: narrow it.

Scope and limits

Redlisten serves public content with no logged in view, so private communities, modmail and user reports are not part of it; those stay with Reddit's own moderator tools. It is read access, so actions such as removing or banning happen on Reddit. What it adds is sight across the whole public site, in comments as well as posts, with the history of each item kept. The docs describe the status fields, and the monitoring page covers delivery options in detail.

Common questions.

Can I see when a post is removed?

Yes. On the native feeds a removed or deleted item is delivered again with status set to removed or deleted, the time the change was observed and, where known, who removed it. The captured text stays.

Can I follow one account across Reddit?

Yes. /user/{name} and the native author endpoints return an account's posts and comments across every public community, and a stream with an authors filter alerts when it posts again.

Does it include private communities or modmail?

No. Redlisten serves public content with no logged in view. Private communities, modmail and user reports stay within Reddit's own moderator tools.

How are alerts delivered?

Per match to a webhook you sign with a secret, to a Slack or Discord channel through an incoming webhook, or as a daily or weekly email digest. Polling with a cursor is always available.

Switch before 13 Nov

Get a key, change one URL, and your feeds, bots and alerts keep running. Then try the search Reddit never had.