# Douyin Comment Replies API (https://www.socialcrawl.dev/platforms/douyin/comment-replies)

> Returns the reply thread under one Douyin comment: text, replier, like count, IP region and verification. Every row carries comment.parent_id set to the comment you asked about, so a thread reassembles without guesswork. Get the comment ID from GET /v1/douyin/post/comments.

TL;DR: `GET /v1/douyin/comment/replies` costs 5 credits per reply RETURNED. The call holds `limit x 5` up front - the default limit of 10 holds 50 and the 50 maximum holds 250 - and settles down to the replies actually delivered. Only a comment with a non-zero `engagement.replies` has a thread, so check that on the parent row before spending a call here With `max_pages`, `max_items` or `max_credits`, each page walked is billed at this price (a cached page is free), and `max_credits` caps the total. and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `url` | yes | Douyin video URL or the bare numeric aweme ID the comment sits under. |
| `comment_id` | yes | The comment to expand, taken from the id field of a GET /v1/douyin/post/comments row. Only comments with a non-zero engagement.replies have a thread. |
| `limit` | no | Replies to return, 1 to 50. Default 10. Each reply costs 5 credits and you are charged only for replies returned. |
| `cursor` | no | Continuation token from a previous response's pagination block. Omit for the first page. |
| `since` | no | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| `until` | no | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/douyin/comment/replies" \
  --data-urlencode "url=https://www.douyin.com/video/7681266289940544369" \
  --data-urlencode "comment_id=7682735175344833317" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### Where do I get the comment ID?

From the id field of any row returned by the Douyin comments endpoint. Only comments whose engagement.replies is greater than zero have a thread to open.

### Is the parent link reliable?

Yes, and that is why this is a separate endpoint. The parent is the comment ID you supplied, echoed back on every row, so the link is exact by construction rather than inferred.

### Can I paginate a long thread?

Yes. This endpoint returns a cursor when more replies exist. Pass it back to walk deeper, and stop when no cursor comes back.

### Do replies carry the same fields as comments?

Yes, plus parent_id. You get the text, replier, like count, IP region and verification status in the same canonical comment shape used across every platform.

### Why not just fetch replies with the comments call?

The comments upstream cannot express a reliable parent for a reply, so a thread built from it would attach replies to the wrong comment. This endpoint asks the source that can.

See the full Douyin API: https://www.socialcrawl.dev/platforms/douyin

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- how to get replies to a Douyin comment
- how to rebuild a Douyin comment thread from an API