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

> Returns the replies under one Weibo comment, oldest first, each naming the comment it answers (comment.parent_id), with the province it was posted from, likes and author. Take comment_id from GET /v1/weibo/post/comments. Pass the returned cursor for the next page.

TL;DR: `GET /v1/weibo/comment/replies` costs 5 credits per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `comment_id` | yes | The comment id, comment.id on GET /v1/weibo/post/comments. |
| `limit` | no | Replies to return, 1 to 20. Default 20. |
| `cursor` | no | Continuation token from a previous response's pagination block, passed back with the same parameters. 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/weibo/comment/replies" \
  --data-urlencode "comment_id=5361992540099003" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I get the replies to a Weibo comment?

Call GET /v1/weibo/comment/replies with comment_id, which is comment.id from GET /v1/weibo/post/comments. Pass the returned cursor for the next page.

### What does each Weibo reply include?

Each reply names the comment it answers in comment.parent_id and carries the province it was posted from, its likes and the author.

### In what order do replies come back?

Oldest first, so the thread reads in the order people wrote it.

### Where do I find the comment_id?

In the response of GET /v1/weibo/post/comments, where each comment has an id field. Pass that value as comment_id here.

### How much does this Weibo endpoint cost?

Each call costs 5 credits on the advanced tier. There is no subscription, and 100 free credits cover 20 calls.

See the full Weibo API: https://www.socialcrawl.dev/platforms/weibo

## 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 do I read the replies under a Weibo comment with an API?
- Does SocialCrawl return threaded Weibo comment replies?