Dcard Topics & Trends — Public Posts & Analytics

What is Dcard Topics & Trends?

Monitor public Dcard topics without an account. Each dataset row represents one topic and combines its public topic metadata with small latest and trending post samples.

The Actor reads logged-out SSR, Next.js hydration, and visible HTML. It does not collect profiles, author names, schools, departments, post bodies, or other personal fields.

Documentation

What you get

Field	Meaning
topicName	Public topic label
topicUrl	Canonical public topic URL
followerCount	Public follower count, when Dcard exposes it
postCount	Public topic post count, when exposed
latestPosts	Sampled latest posts with URL, title, date, and public engagement
trendingPosts	Sampled popular/trending posts with the same fields
observedPostCount	Unique posts actually present in the two samples
observedEngagementCount	Sum of exposed likes, comments, and shares across observed posts
observedAverageEngagement	Average over posts whose engagement was exposed
observedMaxEngagement	Highest exposed sampled-post engagement

Poll summaries appear inside a sampled post only when Dcard exposes an actual poll object. Missing counts remain null; the Actor does not estimate them.

How do I monitor public Dcard topics?

1. Click Try for free.
2. Keep the prefilled public 省錢 topic for a quick preview, or paste known topic URLs.
3. Choose the topic limit and sample size.
4. The quick default returns topic-level counts without a post crawl. Raise the sample size to collect trending posts, and enable latest sampling when needed.
5. Click Start, then open the dataset.

Sample input:

{
  "topicUrls": ["https://www.dcard.tw/topics/%E7%9C%81%E9%8C%A2"],
  "maxItems": 1,
  "samplePostsPerTopic": 0,
  "includeLatest": false,
  "includeTrending": true
}

For known topics:

{
  "topicUrls": [
    "https://www.dcard.tw/topics/AI",
    "https://www.dcard.tw/topics/%E6%97%85%E9%81%8A"
  ],
  "maxItems": 2,
  "samplePostsPerTopic": 10,
  "includeLatest": true,
  "includeTrending": true
}

Illustrative output

{
  "topicName": "AI",
  "topicUrl": "https://www.dcard.tw/topics/AI",
  "followerCount": 12345,
  "postCount": 987,
  "latestPosts": [
    {
      "id": 260002,
      "url": "https://www.dcard.tw/f/3c/p/260002",
      "title": "AI 工具實測",
      "forumAlias": "3c",
      "createdAt": "2026-10-02T00:00:00.000Z",
      "likeCount": 12,
      "commentCount": 4,
      "shareCount": null,
      "engagementCount": 16
    }
  ],
  "trendingPosts": [],
  "observedPostCount": 1,
  "observedEngagementPostCount": 1,
  "observedLikeCount": 12,
  "observedCommentCount": 4,
  "observedEngagementCount": 16,
  "observedAverageEngagement": 16.0,
  "observedMaxEngagement": 16
}

How are the metrics calculated?

Aggregates use only unique posts returned in latestPosts and trendingPosts. A post present in both lists is counted once. Engagement is the sum of whichever public like, comment, and share counts Dcard exposed for that post. The Actor does not extrapolate from the sample to the whole topic.

Export and API

Download finished datasets as JSON, CSV, Excel, XML, or RSS from the dataset Export menu.

Run through the API:

curl -X POST "https://api.apify.com/v2/acts/bakos_bence~dcard-topics-trends/runs?token=YOUR_TOKEN&waitForFinish=120" \
  -H "Content-Type: application/json" \
  -d '{"topicUrls":["https://www.dcard.tw/topics/%E7%9C%81%E9%8C%A2"],"maxItems":1,"samplePostsPerTopic":0,"includeLatest":false,"includeTrending":true}'

Read the resulting defaultDatasetId, then fetch:

https://api.apify.com/v2/datasets/DATASET_ID/items?format=json&clean=true&token=YOUR_TOKEN

The default dataset also connects to Google Sheets, Excel, Zapier, Make, n8n, Power BI, Tableau, Qlik, webhooks, and MCP clients through Apify integrations.

Reliability and limits

• Apify UNBLOCKER is forced because Dcard challenges datacenter traffic.
• A slow or blocked default request is hedged on one fresh proxy session, keeping both attempts inside one bounded timeout window.
• Runs fail instead of succeeding with an empty dataset.
• Resume state prevents already-saved topic rows from being charged again.
• Public page structure can change; unavailable public fields remain null.

This Actor uses public logged-out pages only and is not affiliated with Dcard.