How do I select useful Reddit product discussions before reading comments?
To find Reddit discussions worth reading, pick two communities that match your product question and fetch one page of newest posts from each community with reddit.app.fetch_subreddit_feed and sort:"NEW". Record why each candidate post fits the question, then select up to three posts for comment review. If you already have a post link, go straight to comment review.
For note-sync research, prefer posts that name a device, an action and an outcome. “My desktop does not show edits I made on my phone” gives you more to investigate than a title that only mentions sync.
What makes a discussion worth selecting?
Use scores and comment counts to decide reading order, and write each selection reason as the research question the thread helps answer. A relevant low-score post can still be useful; a high score does not establish a customer problem.
Read the outputs
posts.csv lists the candidate posts. sources.json and coverage.json record where each saved page came from and what the pages cover. After you add chosen native post IDs and reasons, prepare_reddit_threads.py writes selected-comment-requests.json, the plan for comment retrieval.
To hand the shortlist to an assistant connected to BeatAPI, use this instruction:
Review the NEW pages of these two relevant communities for note-sync discussions. Select at most three threads, explaining the usage context and why comments are worth reading. Keep identifiers and sources. Deliver the shortlist before reading the selected discussions.
Steps 1–5 below retrieve the feed pages, build the candidate list, record selection reasons and hand the selected posts to the comment workflow. Building the list runs locally. Write research conclusions after you review the comment evidence.
1. Define community and budget before collecting
Record the product task and why each chosen community is relevant. Request reddit.app.fetch_subreddit_feed with subreddit_name without r/, sort NEW, language en-US and need_format false. The community feed is not a keyword search. The feed input has no time-range field, so do not label a NEW page as all-time or this-year top posts.
Two feed pages plus up to three comment pages make at most five planned data requests. Estimate the cost with current pricing; additional pages, replies and model analysis are separate. Reuse saved responses. To see the current inputs and price of data:reddit.app.fetch_subreddit_feed, call the free Inspect endpoint:
2. Save a first-page response with its original parameters
Replace SaaS with your selected community, and judge relevance from the community’s posts, not from the community name alone. Save the request as request-feed.json:
After you approve the cost, send the request and save the headers and response:
Keep the HTTP status, the request file and the actual collection time. Use a separate request file and directory for the second community. A failed response is not an empty feed: do not retry automatically and do not add pages. If you already have the saved pages, skip this step.
3. Export the saved feed without guessing fields
In the saved response, posts are in data.subredditV3.elements.edges. One post’s title, author, creation time, score and comment count can sit in different node.cells entries. prepare_reddit_threads.py joins only those five fields, rejects conflicting cell values, keeps missing values and negative scores, and excludes elements whose adPayload is not null. Only native t3_ IDs become selectable posts; the script counts other element IDs as unusable instead of converting the element IDs into invented post IDs.
Create feed-inputs.json from the exact request parameters and the actual collection time, and replace the example time with your recorded value. Leave selected empty on the first run:
Save the script below as prepare_reddit_threads.py and run python3 prepare_reddit_threads.py feed-inputs.json feed-review. The script writes posts.csv, sources.json, coverage.json, raw-N.json and an empty selected-comment-requests.json, and makes no network call.
4. Select evidence-bearing discussions, not just high scores
Read each title and open the generated post link to check the context. Select posts about the product task itself, not every post that mentions the brand name. In posts.csv:
scoreis not a customer count.post_linkis a canonical link built from the native post ID, not a permalink returned by the API.response_positionis the order in the feed, not an official score rank.source_communityrecords the community the post was retrieved from, not a verified author affiliation.
Copy the manifest, add up to three exported post IDs with nonempty selection reasons to selected, and run the script again into a new directory. The entry below shows the syntax:
Replace the placeholder with a real exported ID; the script rejects the placeholder. The script also rejects IDs that are not in posts.csv, duplicate selections and more than three selections. A community that returns no usable posts stays recorded in sources.json and coverage.json; an empty result is not a reason to buy more pages. Check why elements were excluded before you draw conclusions.
5. Move selected requests into the comment-evidence workflow
Each entry in selected-comment-requests.json is an unsent request plan that carries the source request ID, the source hash and the selection reason. After you approve a request, send only the entry’s action and params as the API body; the reason and provenance fields stay local.
Save each comment response in its own file, then run export_comments.py, merge_pages.py and reddit_review.py from the complete comment guide. The three scripts keep quote evidence, missing parents, removal status and reviewed/unreviewed coverage, and produce question-backlog.json. Read the conversation before you label a comment as a complaint, question or praise; a title alone does not establish a pain point.
prepare_reddit_threads.py handles one saved first page per community; the script does not follow endCursor and does not set up monitoring. When the same post ID appears twice, posts.csv keeps the first observation and every source snapshot stays saved. The hashes identify local bytes; the hashes do not prove server authenticity or the accuracy of recorded times. Hand over the original fields, the query scope, the selection reasons and the later comment evidence together for the final review.
How can I select top discussions across all time or the past year?
To find long-running community discussions, request a TOP sample with reddit.app.fetch_subreddit_post_channels, an action separate from the NEW feed:
ALL covers all time and YEAR covers the platform’s year window. For a calendar-year study, filter by each post’s publication date and report the date filter. reddit.app.fetch_subreddit_post_channels has no public continuation input and no fixed output contract, so check whether the response contains identifiable posts and scores. Save TOP responses separately from the NEW feed pages that prepare_reddit_threads.py handles. For confirmed posts, continue with the comment workflow.

