Reddit

View API reference · Tag Reddit

We built Reddit coverage for community research: where a market already talks, which threads are moving, and what people write in the comments. Global search finds posts across Reddit; subreddit routes zoom into one community.

This is similar to Reddit search or a subreddit's Hot / New / Top / Rising feed, or an old.reddit thread — posts and nested comments as structured fields.

Inputs and pagination

Every list route returns nextPageToken. Send it back on the next call in the nextPageToken field; omit it on the first page. When it comes back null, there are no more pages.

Comments come back as a depth-first flat list rather than a nested tree. Each entry carries parentCommentId — null for a top-level comment, otherwise the comment it replies to. Group on that field to rebuild the thread. Paging walks top-level comments, and each one brings its nested replies with it.

What you can call

Example — POST /v1/reddit/search:

{
  "apiKey": "YOUR_API_KEY",
  "query": "bounced emails outbound",
  "sort": "top",
  "timeframe": "month"
}

Using it effectively

Find the community before you commit to it. Run redditSearch on your category language first. The subreddits that keep appearing in the results are the ones worth monitoring; that is cheaper than guessing subreddit names and paging feeds that turn out to be dead.

Sort for the question you are asking. top with a timeframe of month or year gives you the threads that defined a topic. new and rising give you what is happening today. relevance is the right default when you are searching rather than browsing.

Read comments, not just titles. A post title is a headline. The thread underneath is where people describe the actual problem in their own words, which is what makes Reddit useful for messaging and product research.

Search costs nothing when it finds nothing. A redditSearch query with no matching posts returns an empty list and is not charged, so you can probe several phrasings cheaply before committing to paging.

Budget your comment paging. A busy thread runs to many pages and each one is billed. Decide up front how deep you need to go.

Use cases

Mine a category's complaints for messaging. Call redditSearch with the problem language your buyers use, sort: "top", timeframe: "year". Take the highest-scoring threads and call redditPostComments on each with the postUrlOrId from the results. The recurring phrasings in those comments are your outbound copy.

Run a daily digest on your ICP's communities. Once you know the three or four subreddits that matter, call redditSubredditPosts on each with sort: "rising" on a schedule and diff against yesterday's post IDs. New entries are conversations you can still be early to.

Size a community before investing in it. Call redditSubredditPosts with sort: "top" and timeframe: "month" and look at the score and comment counts. A subreddit where the top monthly post has single-digit comments is not worth a content programme.

Track a competitor mention. Run redditSubredditSearch for a competitor name inside the communities you already care about, rather than redditSearch across all of Reddit, so you are not drowning in unrelated subreddits.

Credits

Every Reddit call costs 2 credits per page of results. Paging a thread four pages deep costs 8 credits, not 2. Searches that match nothing are not charged. Each route allows 300 requests per minute; HTTP 429 means slow down rather than fan out. chargeInfo on the response is the authoritative amount — see Billing.

Reaching the people you find

Reddit usernames are pseudonymous and there is no Reddit-handle → LinkedIn operation. To contact someone you found in a thread you need a real name or a LinkedIn URL from somewhere else — see GitHub → LinkedIn and X → LinkedIn for the two identity bridges that do exist.

Related: Social media APIs · X (Twitter) · Webhooks