Skip to main content
Illustrative community research workstation showing a fictional post and nested replies
All use cases

PUBLIC DISCUSSIONS / ACCESS REVIEW REQUIRED

Reddit post
data.

Follow the thread.
Keep the context.

Plan a source-linked dataset of posts and replies, with conversation structure and collection limits made explicit.

Discuss access Explore the data

RESEARCH THE DISCUSSION, NOT THE PERSON

Listen to the question.
Understand the replies.

Shape an approved workflow around selected communities and topics. Preserve source context without turning public discussions into individual profiles.

Explore product questions

Organise recurring questions and feedback within an agreed source set, keeping any permitted analysis connected to the underlying discussion.

Understand conversation structure

Separate the original post, top-level responses and nested replies. Keep disagreement and follow-up context attached to the right parent.

Measure a defined collection

Report which records were returned, which branches remain incomplete and what the selected sort and time window actually cover.

A DATA MODEL THAT PRESERVES THE THREAD

The post. The reply.
The missing pieces.

Keep content records and collection evidence together. Missing values, partial branches and permissions should never be hidden behind a clean JSON file.

Start with the discussion.

Keep a post connected to its community, stable identifier and source URL. Separate the post itself from the replies collected later.

post_id / subreddit / url
The post identity and community context.
title / body / content_state
Available post content with explicit missing or removed states.
score / reported_comment_count
Observed metrics, not exact vote totals or collected reply counts.
created_at / observed_at
Source creation time and the time of collection.
post.json

Illustrative schema / not a collected Reddit result

{
  "example_only": true,
  "record_type": "post",
  "source": "Reddit",
  "post_id": "t3_example",
  "subreddit": "examplecommunity",
  "url": null,
  "title": "Which onboarding step needs a clearer explanation?",
  "body": "A fictional discussion about improving a product onboarding flow.",
  "content_state": "visible",
  "author": null,
  "score": null,
  "reported_comment_count": null,
  "created_at": null,
  "observed_at": null,
  "comments_included": false
}

Fictional records and values. No live data request.

Fictional identifiers and content. This is a proposed delivery schema, not a live Reddit result or a built-in Scraping API response.

Illustrative delivery schemas, not collected Reddit records or a built-in API response. Live access and production delivery have not been established for this source.

SMALL DISTINCTIONS, BETTER DATA

Keep the thread
intact.

A record is useful when its relationships, metrics and limits are clear. More rows do not automatically mean better coverage.

01 / RELATIONSHIP

A reply has a parent

Preserve comment, parent and root post identifiers. A flattened text dump cannot reliably explain who replied to what.

02 / COVERAGE

A count is not the content

A reported comment count is separate from retrieved replies. Unexpanded branches remain explicitly incomplete.

03 / LIFECYCLE

A snapshot is not permanent

Plan for edits, deletions and changing availability. Retention and removal handling follow the approved access terms.

APPROVED ACCESS COMES FIRST

Validate the route.
Then design the collection.

There is no verified self-serve Reddit collection route here today. We scope the work around approved access, not promises to bypass a block.

  1. 01 / ACCESS

    Confirm the permitted use

    Review Reddit approval, commercial permissions and data handling obligations. Technical reachability does not grant those rights.

  2. 02 / SCOPE

    Retrieve only what is needed

    Prefer structured records from an approved API. Define communities, sorting, fields and reply depth; avoid unnecessary page rendering or AI calls.

  3. 03 / MAINTAIN

    Respect limits and removals

    Use bounded pagination and explicit stopping conditions. Track access failures and apply the required content and author-deletion handling.

STRUCTURED ACCESS

Reddit Data API

Reddit documents post listings, comment trees and additional-comment retrieval. Approval, OAuth and the appropriate commercial agreement must be established separately.

Reddit API access guidance
COLLECTION ECONOMICS

Reduce unnecessary requests

Validate access before scaling. Collect a bounded set of fields and expand only the required threads. Provider request prices do not include Reddit access or licensing fees.

Reddit Data API Terms

Our tested scraping provider rejected Reddit. We do not present proxy rotation, alternate hostnames or CAPTCHA handling as an approved access route. Review Reddit's Responsible Builder Policy.

DIFFERENT SERVICES, DIFFERENT ACCESS REQUIREMENTS

Choose the right
starting point.

Our general API and a managed Reddit project are not interchangeable. Reddit-specific delivery begins with an access and feasibility review.

FOR OTHER SUPPORTED PUBLIC PAGES

Scraping API

Run your own requests against supported public sources. This is not a currently validated Reddit connector.

  • Content-only mode without AI processing
  • Your URLs, parsing and result handling
  • No CAPTCHA or login bypass
Explore the general API
ACCESS REVIEW BEFORE DELIVERY

Managed Reddit data

Discuss an approved collection workflow. Availability and pricing are confirmed only after access and sample validation.

  • Permission and source-scope review
  • Post/reply relationships and coverage evidence
  • Agreed retention, removal and delivery rules
Discuss your Reddit requirements

BEFORE YOU BUILD ON THE DATA

Reply trees, coverage
and access.

Can I run Reddit URLs through your Scraping API now?

The current self-serve provider route rejected Reddit in our validation, so we do not offer it as a working Reddit connector. An HTTP 200 page shell or a public URL is not proof of data access. A managed project starts with an access review; Reddit API approval and any required commercial agreement are separate.

Does a post listing include all comments and replies?

No. Listing metadata can include a reported comment count without any comment text. Comment trees may contain collapsed branches and more-comment placeholders. We define which threads and depths are in scope and report partial results rather than claim a complete discussion from one response.

How do you preserve the reply hierarchy?

Keep each comment identifier, its immediate parent identifier and its root post identifier. In Reddit's documented structure, t1 identifies a comment and t3 a post. A reply to a comment must remain distinct from a top-level reply. Ordering and depth refer to the retrieved tree, not a reconstructed full history.

Are scores exact upvote counts or reliable trend measurements?

A displayed score is not a raw vote ledger. Treat scores and comment counts as observed source metrics, with a timestamp. Ranking, sort mode, moderation and incomplete collection can change what is visible. Do not infer audience size, sentiment or a platform-wide trend from those numbers alone.

Can you deliver a complete subreddit archive?

Not from a single listing or an assumed pagination loop. Coverage depends on approved access, available history, sorting, pagination and thread expansion. We define a collection window and stopping conditions, deduplicate records and label coverage gaps before agreeing a historical or recurring dataset.

What happens to removed content and deleted authors?

Deletion handling is part of the access design, not an optional archive feature. Reddit's API guidance requires removal of deleted user content and author-identifying references when an account is deleted. We do not offer deleted-content recovery or retain deleted text as an anonymized substitute. Storage, refresh and deletion rules must match the approved use.

Can you add topic classification or sentiment labels?

Only where the approved use permits that processing. Derived labels stay separate from original content, with an explicit input scope. Model training is not included. We do not offer sensitive-trait profiling, re-identification or matching pseudonymous Reddit users to off-platform identities.

START WITH AN ACCESS AND SCOPE REVIEW

Which discussions
matter to you?

Share the communities, fields and intended use. Tell us whether approved Reddit API access is already available; do not send credentials in this form.

  • Communities, example URLs and required fields
  • Reply depth, time window and refresh needs
  • Approved use, retention and delivery requirements
Discuss your project

Up to 5,000 characters.

Projects are accepted individually, subject to feasibility and available capacity. An enquiry does not reserve a solution or confirm delivery. Pricing and terms are agreed directly with our team.

This is an access and feasibility enquiry. It does not run a scrape, grant Reddit access or create a paid task.

ScrapingBuddy is not affiliated with Reddit. The workstation image and dataset examples are fictional, not an actual Reddit interface or collected user content. We do not offer private-message collection, private-community bypass, deleted-content recovery or sensitive user profiling.