# Douyin Comments API (douyin.comments)

- Canonical page: https://everyinfra.com/en/douyin-api/comments
- Endpoint: POST https://api.everyinfra.com/api/v1/social with {"platform": "douyin", "action": "comments", "params": {...}}
- Price: $0.000556 per call ($0.56 per 1,000 requests); failed calls and empty results are not charged
- Billing unit: every 20 rows you ask for count as one call; blocks that come back with no rows are not charged
- Returns: list, default 20, max 150 per call
- Pagination: pass next_page_token back as page_token for the next page, other params unchanged; each page is billed by its row count, one call per 20 rows, tokens last 24 hours
- Mode: sync; add "mode": "async" for slow tasks

Douyin Comments reads the comments under one video, given the video's `url`. Each row carries the text, likes, reply count, the commenter's nickname and ID, the IP region and the publish time. Use it to hear what viewers say about a video: sentiment and reputation analysis, product feedback, or finding the most engaged viewers.

A call without `page_token` reads only the first batch of comments, with some replies; to read every top-level comment, start with an empty `page_token` and page through. `liked_by_author` marks comments the video's author liked, and `is_reply` with `reply_to_id` lets you put each reply back under the comment it answers. `ip_location` is the region Douyin displays, not an address the commenter entered.

## Health

- Live health (24h percent, hourly and daily trends): https://api.everyinfra.com/api/v1/social/availability?platform=douyin&action=comments

## Parameters

| name | type | required | default | description |
|---|---|---|---|---|
| url | not declared | yes | not declared | Full URL of the target Douyin video, formatted as `https://www.douyin.com/video/<video_id>`. Fetches video details in `video`, comments in `comments`, the replies under one comment in `comment_replies` (the video the comment sits on), or audio transcripts in `transcript`. Do not pass user profile or search page URLs. |
| page_token | not declared | no | not declared | Page token for `user_posts` and `comments`. To start paging, send an empty string `page_token=""`; then pass back the previous response's `next_page_token` exactly as received to get the next page, keeping every other parameter unchanged. Tokens last 24 hours and only work for the same account and the same parameters; an expired or mismatched token returns 422, so start again from the first page. On the last page the response has no `next_page_token` (`pagination.has_more` is false). Each `user_posts` page is one call and holds up to 100 rows, newest first, and is not filtered by `since` (filter by `posted_at` on your side if you need a date window). `comments` pages hold up to 50 top-level comments and are priced per block of rows: every 20 rows count as one call, so a page counts as 3 calls for its 50 rows (a smaller `limit` counts that many rows), and blocks that come back with no rows are not charged. Without `page_token` the call is a single fetch: `user_posts` returns the newest batch (`since` applies) and `comments` returns only the head of the list, replies included, also at one call per 20 rows: 20 rows by default and at most about 50-60 however high `limit` is, usually with no `next_page_token`. |
| limit | integer (1–150) | no | 20 | The most rows to return in this call, an integer from 1 to 150. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |

## Response fields (items in `results`)

| field | meaning |
|---|---|
| next_page_token | Page token (search / user_posts / comments / comment_replies / billboard_video_hot / billboard_low_fan_explosion / billboard_high_completion / billboard_account_search / music_search): pass it back unchanged as page_token to fetch the next page, keeping the other parameters the same; valid for 24 hours. Every row of a page carries the same value, which also appears at the top level of the response. Absent on the last page. Comment pages walk all top-level comments page by page. |
| id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
| text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
| like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
| reply_count | Replies, usually replies to a comment. null means not disclosed. |
| author_name | Author's display name. |
| author_id | Author's unique ID on the platform. |
| ip_location | IP region Douyin displays (set by the platform, not entered by the user). |
| is_hot | Whether the comment carries Douyin's hot-comment badge (comments). |
| is_reply | Whether the row is a reply. |
| reply_to_id | ID of the top-level comment this reply sits under: on `comments` reply rows, the comment it hangs from; on every `comment_replies` row, the comment you asked about. |
| posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
| video_id | ID of the video the comment belongs to (comments). |
| platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
| liked_by_author | Whether the video's author liked the comment; comments the author liked tend to carry more weight. |
| author_avatar_url | Author avatar image URL: the creator on search, user_posts and video rows, the commenter on comments rows. |
| author_uid | Numeric user ID of the author (on comments, of the commenter). author_id is the secUid; both identify the same person. |
| images | Array of image links in the platform's display order; absent when there are no images. |
| mentioned_users | People @-mentioned in the comment, each with user_id (secUid), uid (numeric ID) and nickname. Absent when nobody is mentioned. |

## Example

```bash
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "douyin",
  "action": "comments",
  "params": {
    "url": "https://www.douyin.com/video/7633646113853104116"
  }
}'
```

```python
import os
import requests

response = requests.post(
    "https://api.everyinfra.com/api/v1/social",
    headers={"Authorization": f"Bearer {os.environ['EVERYINFRA_API_KEY']}"},
    json={
        "platform": "douyin",
        "action": "comments",
        "params": {
            "url": "https://www.douyin.com/video/7633646113853104116",
        },
    },
    timeout=120,
)
print(response.status_code)
print(response.json())
```

## Response example

Real response to the example request above, captured 2026-10-16T13:49:27Z. `results` and `count` are real with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2 of 48. `id`, `billing` and `quota` differ on every call, so only their shape is shown.

```text
{
  "id": "req_…",
  "platform": "douyin",
  "action": "comments",
  "results": [
    {
      "id": "•••",
      "text": "也夸夸我好吗？毕竟辛苦了大半天",
      "like_count": 36613,
      "reply_count": 3920,
      "author_name": "•••",
      "author_id": "•••",
      "ip_location": "•••",
      "liked_by_author": false,
      "is_reply": false,
      "posted_at": "2026-05-16T07:44:26+00:00",
      "author_avatar_url": "https://p3.douyinpic.com/•••",
      "author_uid": "•••",
      "video_id": "7633646113853104116",
      "images": [
        "https://p26-sign.douyinpic.com/tos-cn-i-p14lwwcsbr/0ca1d6122bc04436ae1ef616727fbdc4~tplv-p14lwwcsbr-7.image?lk3s=7b078dd2&x-expires=1792177200&x-signature=3jHJJizWcJ%2FOsppJ8hAkTk5coBQ%3D&from=2064092626&se=false&sc=image&biz_tag=aweme_comment&l=202610162149377E1F6EF12980549AC8D7"
      ],
      "platform": "douyin"
    },
    {
      "id": "•••",
      "text": "女人也可以做漂亮饭[抠鼻][抠鼻][抠鼻][抠鼻]",
      "like_count": 7668,
      "reply_count": 646,
      "author_name": "•••",
      "author_id": "•••",
      "ip_location": "•••",
      "liked_by_author": false,
      "is_reply": false,
      "posted_at": "2026-05-12T15:26:16+00:00",
      "author_avatar_url": "https://p3.douyinpic.com/•••",
      "author_uid": "•••",
      "video_id": "7633646113853104116",
      "images": [
        "https://p26-sign.douyinpic.com/tos-cn-i-p14lwwcsbr/f0e9dd3639b04e57b7d33803eaaeda1e~tplv-p14lwwcsbr-7.image?lk3s=7b078dd2&x-expires=1792177200&x-signature=q4h%2BPvenriDiq5zb5NDE%2Fva2qZo%3D&from=2064092626&se=false&sc=image&biz_tag=aweme_comment&l=202610162149377E1F6EF12980549AC8…"
      ],
      "platform": "douyin"
    }
  ],
  "next_page_token": …,
  "pagination": { … },
  "count": 48,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}
```

## FAQ

### How do I read all the comments on a video?

Send `page_token` as an empty string for the first page, then pass each page's `next_page_token` back unchanged with the other parameters the same. Pages hold up to 50 top-level comments, the last page has no `next_page_token`, and tokens last 24 hours. Comments are paged by popularity, so videos with many comments can come back 20 to 30% short. A call without `page_token` returns only the first 50 to 60 or so comments, replies included. Each block of 20 rows counts as one call, so a full page counts as 3, and empty blocks are free. A token works only with the same account and parameters; an expired or changed one returns a 422, so start again from page one.

### How do I tell replies from top-level comments?

Check `is_reply`: when it is true the row is a reply, and `reply_to_id` is the ID of the comment it answers. With those two fields you can rebuild the thread, while `reply_count` tells you how many replies each comment has. Paging covers top-level comments only; to read every reply under one comment, use the Douyin Comment replies capability with that comment's ID.

### Which comments should I read first?

Start with rows where `liked_by_author` is true: the video's author liked them personally, so they tend to carry the most weight. Then sort by `like_count` to see which views other viewers agree with most.

## Also

- Capability catalog (no key): https://api.everyinfra.com/api/v1/social/catalog?platform=douyin
- OpenAPI: https://everyinfra.com/openapi.json · Agents guide: https://everyinfra.com/agents.md