logo
FR

Douyin Video Comments

Collect public comments, engagement details, author information, and timestamps from one Douyin video

Source · en-USRevenir à la traduction

Aperçu

Public comments on a Douyin video show how viewers react in their own words, which topics trigger replies, and how visible engagement develops around the content. This Data App turns the public comment area of one video into a consistent dataset with comment text, author details, reply relationships, engagement snapshots, and timestamps.

The result is suited to repeatable analysis rather than manual scrolling. It keeps the original comment wording and connects each comment to its video and discussion thread, making it easier to compare reactions, identify recurring themes, and inspect conversations around a post.

Data notes

The data covers comments and author details that are publicly visible for the supplied Douyin video at collection time. Each normal record is identified by its Comment ID, which is used to remove duplicates across collected pages. Private, deleted, restricted, and login-only comments are outside the coverage.

Like count, Favorite count, Repost count, Reply count, View count, author details, and Comment status are snapshots and may change after collection. Count values and several classification values are retained as source text rather than converted into numbers. Comment images are also retained in the source text form supplied with each record. Published at and Collected at preserve the source timestamps without inferring a timezone. Source video ID and No data retain the collection outcome when a video has no public comment result.

What the results look like

Each normal record represents one publicly visible comment from the selected Douyin video.

Comment IDComment textAccount namePublished atLike countReply count
7675002466995684133【探险者】坐进探险者,开启感官之旅[赞][赞]颜西枣A2026-08-17T22:09:2500
7675504408697275187此用户没有填写评价艾杰很哇塞!2026-08-19T06:37:1500

Additional values include account and avatar details, location text, comment and content links, reply-thread identifiers, image information, verification data, recognized speech and on-screen text, and collection time.

Use cases

  • Compare Comment text with Like count and Reply count to identify reactions that generated stronger visible engagement.
  • Group Comment text by recurring phrases, then use Published at to see how the discussion changed over time.
  • Reconstruct reply threads with Parent comment ID and Root comment ID to distinguish top-level reactions from follow-up conversations.
  • Review Account name, Verification type, IP location, and Location cities to describe the visible mix of participants without treating those fields as verified identity data.

Périmètre et limites

Each run accepts one Douyin video ID and an expected count from 1 to 200. Results are returned in complete batches of 20, so the actual count may be rounded up. Only publicly available comments are covered.

  • Adapté pour
  • When you need public comment text and engagement details from a specific Douyin video
  • When you need comment authors, reply relationships, timestamps, and location text for analysis
  • À ne pas utiliser pour
  • When you need comments from a platform other than Douyin
  • When you need private, deleted, restricted, or login-only comments

Gestion des échecs

Comportement en cas d'échec et de nouvelle tentative déclaré par l'auteur. Nous vous recommandons de l'inclure dans votre prompt système lors de l'intégration.

  1. 1If no comments are returned, verify the video ID and confirm that the video and its comments are publicly visible
  2. 2Retry later after rate limiting, temporary service unavailability, or a timeout
  3. 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
  4. 4If authentication fails, verify the API Key configured for the execution environment

Entrée

Paramètres requis pour appeler cette App, générés à partir de l'input.schema du manifest.json.

ChampNom métierTypeRequisDéfautÉnum / ContraintesExempleDescription
video_idDouyin video IDstringOui——7675002361652376997The numeric ID of the Douyin video whose public comments will be collected. Enter the video ID only, not a keyword or URL.
comment_countExpected comment countintegerOui—1–20020The expected number of comments to collect, from 1 to 200. Results are returned and billed in complete batches of 20, so the actual count may be rounded up.

Sortie

Structure des champs d'un enregistrement, générée à partir de l'output.schema du manifest.json.

ChampNom métierTypeExempleDescription
account_idAccount IDstring3751974819070941The Douyin account identifier associated with the comment author
account_nameAccount namestring颜西枣AThe public display name of the comment author
account_short_idAccount short IDstring37519748The author's short Douyin identifier when available
accurate_location_citiesLocation citiesstring北京City-level location text associated with the comment author when available
accurate_location_provincesLocation provincesstring北京Province-level location text associated with the comment author when available
asr_textSpeech transcriptstring坐进探险者,开启感官之旅Speech recognition text associated with the referenced content when available
avatar_urlAvatar URLstringhttps://p3-pc.douyinpic.com/aweme/100x100/aweme-avatar/tos-cn-i-0813c000-ce_oUnA4rIiXJAIIAW2AT2QfevAAkDoAw8H8fRMQeThe public avatar image URL of the comment author
biz_idBusiness IDstring7675002361652376997The business identifier carried by the source comment record
collect_countFavorite countstring0The favorite count associated with the comment at collection time, retained as source text
comment_idComment IDstring7675002466995684133The stable unique identifier of the Douyin comment
comment_image_url_listComment imagesstring[]The comment image URL collection retained in the source text form
comment_textComment textstring【探险者】坐进探险者,开启感官之旅[赞][赞]The text published in the Douyin comment
comment_typeComment typestring1The source value identifying the comment type
comment_urlComment URLstringhttp://www.douyin.com/video/7675002361652376997The public URL associated with the comment when available
content_idContent IDstring7675002361652376997The identifier of the Douyin video associated with the comment
crawl_timeCollected atstring2026-08-25T14:02:54The source timestamp when the comment record was collected
fansFollower countstring1200The author's follower count at collection time, retained as source text
ip_locationIP locationstring北京The location text shown for the comment when available
like_countLike countstring0The comment like count at collection time, retained as source text
ocr_textOn-screen textstring探险者Text recognized from the referenced content when available
parent_comment_idParent comment IDstring7675002466995684133The identifier of the direct parent comment for a reply
publish_timePublished atstring2026-08-17T22:09:25The source timestamp when the comment was published
repost_countRepost countstring0The repost count associated with the comment at collection time, retained as source text
root_comment_idRoot comment IDstring7675002466995684133The identifier of the root comment in the reply thread
statusComment statusstringactiveThe comment status observed at collection time
sub_comment_countReply countstring0The number of replies to the comment, retained as source text
source_video_idSource video IDstring7675002361652376997The submitted Douyin video ID associated with the result record
no_dataNo databooleanfalseWhether no public comment data was collected for the source video
verify_typeVerification typestring0The author's verification type retained as source text when available
view_countView countstring0The view count associated with the referenced content at collection time, retained as source text

Schema de l'enregistrement

La sortie est renvoyée enregistrement par enregistrement. detail.output.idFieldHint

output.schema
{
  "type": "object",
  "properties": {
    "account_id": {
      "type": "string",
      "title": "Account ID",
      "description": "The Douyin account identifier associated with the comment author",
      "prefill": "3751974819070941"
    },
    "account_name": {
      "type": "string",
      "title": "Account name",
      "description": "The public display name of the comment author",
      "prefill": "颜西枣A"
    },
    "account_short_id": {
      "type": "string",
      "title": "Account short ID",
      "description": "The author's short Douyin identifier when available",
      "prefill": "37519748"
    },
    "accurate_location_cities": {
      "type": "string",
      "title": "Location cities",
      "description": "City-level location text associated with the comment author when available",
      "prefill": "北京"
    },
    "accurate_location_provinces": {
      "type": "string",
      "title": "Location provinces",
      "description": "Province-level location text associated with the comment author when available",
      "prefill": "北京"
    },
    "asr_text": {
      "type": "string",
      "title": "Speech transcript",
      "description": "Speech recognition text associated with the referenced content when available",
      "prefill": "坐进探险者,开启感官之旅"
    },
    "avatar_url": {
      "type": "string",
      "title": "Avatar URL",
      "description": "The public avatar image URL of the comment author",
      "prefill": "https://p3-pc.douyinpic.com/aweme/100x100/aweme-avatar/tos-cn-i-0813c000-ce_oUnA4rIiXJAIIAW2AT2QfevAAkDoAw8H8fRMQe"
    },
    "biz_id": {
      "type": "string",
      "title": "Business ID",
      "description": "The business identifier carried by the source comment record",
      "prefill": "7675002361652376997"
    },
    "collect_count": {
      "type": "string",
      "title": "Favorite count",
      "description": "The favorite count associated with the comment at collection time, retained as source text",
      "prefill": "0"
    },
    "comment_id": {
      "type": "string",
      "title": "Comment ID",
      "description": "The stable unique identifier of the Douyin comment",
      "prefill": "7675002466995684133"
    },
    "comment_image_url_list": {
      "type": "string",
      "title": "Comment images",
      "description": "The comment image URL collection retained in the source text form",
      "prefill": "[]"
    },
    "comment_text": {
      "type": "string",
      "title": "Comment text",
      "description": "The text published in the Douyin comment",
      "prefill": "【探险者】坐进探险者,开启感官之旅[赞][赞]"
    },
    "comment_type": {
      "type": "string",
      "title": "Comment type",
      "description": "The source value identifying the comment type",
      "prefill": "1"
    },
    "comment_url": {
      "type": "string",
      "title": "Comment URL",
      "description": "The public URL associated with the comment when available",
      "prefill": "http://www.douyin.com/video/7675002361652376997"
    },
    "content_id": {
      "type": "string",
      "title": "Content ID",
      "description": "The identifier of the Douyin video associated with the comment",
      "prefill": "7675002361652376997"
    },
    "crawl_time": {
      "type": "string",
      "title": "Collected at",
      "description": "The source timestamp when the comment record was collected",
      "prefill": "2026-08-25T14:02:54"
    },
    "fans": {
      "type": "string",
      "title": "Follower count",
      "description": "The author's follower count at collection time, retained as source text",
      "prefill": "1200"
    },
    "ip_location": {
      "type": "string",
      "title": "IP location",
      "description": "The location text shown for the comment when available",
      "prefill": "北京"
    },
    "like_count": {
      "type": "string",
      "title": "Like count",
      "description": "The comment like count at collection time, retained as source text",
      "prefill": "0"
    },
    "ocr_text": {
      "type": "string",
      "title": "On-screen text",
      "description": "Text recognized from the referenced content when available",
      "prefill": "探险者"
    },
    "parent_comment_id": {
      "type": "string",
      "title": "Parent comment ID",
      "description": "The identifier of the direct parent comment for a reply",
      "prefill": "7675002466995684133"
    },
    "publish_time": {
      "type": "string",
      "title": "Published at",
      "description": "The source timestamp when the comment was published",
      "prefill": "2026-08-17T22:09:25"
    },
    "repost_count": {
      "type": "string",
      "title": "Repost count",
      "description": "The repost count associated with the comment at collection time, retained as source text",
      "prefill": "0"
    },
    "root_comment_id": {
      "type": "string",
      "title": "Root comment ID",
      "description": "The identifier of the root comment in the reply thread",
      "prefill": "7675002466995684133"
    },
    "status": {
      "type": "string",
      "title": "Comment status",
      "description": "The comment status observed at collection time",
      "prefill": "active"
    },
    "sub_comment_count": {
      "type": "string",
      "title": "Reply count",
      "description": "The number of replies to the comment, retained as source text",
      "prefill": "0"
    },
    "source_video_id": {
      "type": "string",
      "title": "Source video ID",
      "description": "The submitted Douyin video ID associated with the result record",
      "prefill": "7675002361652376997"
    },
    "no_data": {
      "type": "boolean",
      "title": "No data",
      "description": "Whether no public comment data was collected for the source video",
      "prefill": false
    },
    "verify_type": {
      "type": "string",
      "title": "Verification type",
      "description": "The author's verification type retained as source text when available",
      "prefill": "0"
    },
    "view_count": {
      "type": "string",
      "title": "View count",
      "description": "The view count associated with the referenced content at collection time, retained as source text",
      "prefill": "0"
    }
  },
  "required": [],
  "additionalProperties": false
}

Intégration

Cette App peut être intégrée via MCP, API, SDK ou export de fichiers — tous les canaux partagent les mêmes capacités et la même tarification. Chaque requête s'authentifie avec l'en-tête Authorization: Bearer à l'aide d'une API Key (longue durée, créée dans la console Data Hub) ; les clients MCP peuvent aussi se connecter via OAuth, sans clé. D'autres options comme la CLI et Skill arrivent bientôt.

Avec MCP (Model Context Protocol), vous pouvez appeler cette App directement depuis des clients IA comme Claude et Cursor. Choisissez votre client et votre mode d'authentification, puis copiez la config ci-dessous.

Config du client

Remplacez la valeur après Bearer par votre API Key longue durée. Fonctionne dans n'importe quel client, en CI ou en environnement sans navigateur.

mcpServers config
{
  "mcpServers": {
    "meme_today__douyin-video-comments": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=meme_today/douyin-video-comments",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

Laissez l'IA tout configurer pour vous

Vous ne voulez pas modifier les configs à la main ? Copiez le prompt d'installation et collez-le dans n'importe quel client IA — il effectuera la configuration à sa manière. (Le prompt demande à l'IA de vous réclamer votre API Key, afin que les identifiants ne finissent jamais dans l'historique de conversation ni dans des configs partagées.)

detail.access.mcp.composeHint

Tarifs

Task start

Facturé une fois par exécution soumise, quel que soit le nombre d'enregistrements renvoyés.

0,0001 $US/ exécution
20 returned comments

Facturé selon le nombre d'enregistrements renvoyés avec succès. Les exécutions échouées ne sont pas facturées. Facturé par unités de 20 enregistrement ; toute unité incomplète est arrondie à 20 enregistrement.

0,003 $US/ 20 enregistrement

Plusieurs événements de facturation se cumulent indépendamment. Voir chaque élément pour les détails. Les exécutions échouées ne sont pas facturées.

Voir les crédits

Essayer maintenant

Renseignez les paramètres et lancez l'exécution — les résultats proviennent d'un appel réel.

Exemple
Les paramètres sont validés par rapport à l'input.schema avant la soumission
Veuillez d'abord renseigner les paramètres requis
À partir de 0,003 $US / 20 enregistrement