Dcard Full Threads — Posts & Nested Public Replies

What does Dcard Full Threads do?

Export public Dcard discussions as one dataset row per thread, ready for bounded conversation analysis or moderation review.

• Post text, forum, timestamps, media URLs, and engagement counts
• Root comments with recursive nested replies in their original hierarchy
• Honest expected, returned, truncated, and error metadata for every thread

Only public logged-out data is read. School, department, gender, avatar, identity, nickname, and other natural-person profile fields are removed.

Documentation

Field	What it contains	Example
id	Public thread ID	262047730
url	Stable public thread URL	https://www.dcard.tw/f/mood/p/262047730
title	Public thread title	Public thread
content / excerpt	Public post text	Public body
forumId / forumAlias / forumName	Public forum identifiers	mood
topics / tags	Public thread classifications	["discussion"]
createdAt / updatedAt	Post timestamps	2026-01-01T00:00:00.000Z
likeCount / reactionCount	Post engagement totals	10 / 7
reactions	Reaction-type counts	{"heart": 7}
shareCount / quoteCount / collectionCount	Other engagement totals	2 / 1 / 3
commentCount / totalCommentCount	Dcard's exposed comment totals	2 / 2
mediaUrls	Public post media links	["https://..."]
nsfw / pinned	Public post flags	false / false
moderation	Visible deletion and moderation state	{"state": "visible"}
postCompleteness	Whether full post content was available, plus its public source	{"complete": false, "source": "public_feed_summary"}
comments	Root comments with recursive replies	[{"depth": 0, "replies": [...]}]
commentsCompleteness	Counts, bounds, errors, and completeness verdict	{"expected": 2, "returned": 2, "complete": true}

How do I export full Dcard threads?

1. Click Try for free.
2. The default returns one public Mood-forum thread with comments disabled, keeping the first run quick and bounded.
3. Paste specific Thread URLs or other forum aliases and raise the comment limit when you need full post detail and recursive replies.
4. Click Start, then open the dataset and export JSON, CSV, or Excel.

Input

Field	Purpose	Default
threadUrls	Public Dcard thread URLs or post IDs	empty
forums	Forum aliases used when URLs are empty	mood
maxThreads	Maximum dataset rows	1
maxCommentsPerThread	Combined root and nested comment bound; raise above zero to collect replies	0
maxDepth	Deepest retained reply level; roots are depth 0	8
maxRepliesPerComment	Nested replies retained under one parent	100
includeNsfw	Include public threads marked NSFW	false

Specific thread URLs take priority over forum feeds. The Start default uses the public Mood board. If that feed is empty or blocked, the Actor falls back to Dcard's global popular feed, then to a public topic page. Summary-only post data is marked incomplete in postCompleteness; it is never presented as a full post.

Illustrative output

Each dataset item is one thread:

{
  "id": 262047730,
  "url": "https://www.dcard.tw/f/mood/p/262047730",
  "title": "Public thread",
  "forumAlias": "mood",
  "likeCount": 10,
  "reactionCount": 7,
  "shareCount": 2,
  "quoteCount": 1,
  "comments": [
    {
      "id": "root-comment-id",
      "parentId": null,
      "depth": 0,
      "floor": 1,
      "content": "Root comment",
      "subCommentCount": 1,
      "replies": [
        {
          "id": "reply-id",
          "parentId": "root-comment-id",
          "depth": 1,
          "floor": 1,
          "content": "Nested reply",
          "replies": []
        }
      ]
    }
  ],
  "commentsCompleteness": {
    "expected": 2,
    "returned": 2,
    "rootReturned": 1,
    "nestedExpected": 1,
    "nestedReturned": 1,
    "complete": true,
    "truncated": false,
    "errors": []
  }
}

Every comment includes parentId, depth, floor, subCommentCount, like/reaction/share/quote counts, timestamps, and visible deletion or moderation state.

Comment field	What it contains
id / postId / parentId	Comment, thread, and parent relationships
depth / floor	Recursive depth and Dcard floor
content / timestamps	Public comment text and timing
engagement counts	Likes, reactions, shares, and quotes
subCommentCount / replies	Expected direct children and recursively nested rows
moderation	Visible, hidden, in-review, or deleted state

How should I read completeness?

commentsCompleteness.complete is true only when pagination ended normally, no request failed, no configured bound was hit, and the returned count satisfies Dcard's expected count when one is exposed.

It is always false when:

• maxCommentsPerThread, maxDepth, or maxRepliesPerComment cuts the tree
• a root-comment or nested-reply request fails
• Dcard reports more comments than the Actor returned

Use expected, returned, truncated, and errors to decide whether a row is suitable for completeness-sensitive work. A bounded row remains useful, but is never mislabeled as complete.

Privacy and access

The Actor reads public pages and public API responses without an account. It does not access member-only or login-gated content. Output intentionally excludes:

• school, department, and gender
• avatar and natural-person display/profile fields
• persona IDs, nicknames, and identity metadata

Thread and comment IDs remain because they identify public content, preserve hierarchy, and support deduplication.

Reliability, proxy, and resume behavior

The Actor manages Apify UNBLOCKER automatically. Retries stay on a sticky session briefly, rotate on a bounded schedule, and stop at the run's HTTP-attempt budget.

Rows are pushed as each thread finishes. Resume state remembers saved thread IDs, so a migrated or resurrected run does not save and charge the same thread again. If the run's charge limit is reached, the Actor stops before processing another row.

How much does it cost?

The Actor is designed for pay-per-result billing: one result is one thread row, regardless of the number of comments nested inside it. Current rates will appear on the Pricing tab after monetization is configured.

FAQ

Why is a thread marked incomplete?

Check commentsCompleteness.errors and limits. The Actor either hit a configured bound, received fewer comments than Dcard advertised, or could not finish a public request.

Why are profile fields missing?

They are intentionally excluded. This Actor is for thread content and conversation structure, not profiling individual users.

Can I use this as a standing forum mirror?

No. Use bounded, customer-directed thread or forum inputs. The Actor is not designed for continuous bulk mirroring of Dcard content.

This Actor is not affiliated with Dcard.