> **For coding agents and LLMs:** This is one page from the Social Fetch docs (markdown export). For curated orientation and workflow guidance, start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for agent onboarding and crawl rules, use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for the full endpoint list with links to pages like this one, use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt); for one platform's parameters and curls, use [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt); use [`/llms.json`](https://www.socialfetch.dev/llms.json) when you need structured JSON for tool registration.

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/docs/api/v1/weibo/posts/postid/comments/get>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/docs/api/v1/weibo/posts/postid/comments/get.mdx>

## API base URL and authentication

- **API origin (from OpenAPI `servers`):** `https://api.socialfetch.dev`
- **Authentication:** send `x-api-key: sfk_...` on `/v1/**` and `/v2/**` routes unless the operation is explicitly anonymous (check OpenAPI `security`, the [API reference hub](https://www.socialfetch.dev/docs/api.mdx), [`/llms.txt`](https://www.socialfetch.dev/llms.txt), or [`/llms.json`](https://www.socialfetch.dev/llms.json) for each route).
- **OpenAPI JSON:** <https://www.socialfetch.dev/openapi.json>

## Recommended docs entrypoints (this site)

- [Documentation overview](https://www.socialfetch.dev/docs.mdx) — top-level orientation (markdown).
- [Quickstart](https://www.socialfetch.dev/docs/quickstart.mdx) — authenticate with `x-api-key`, validate auth with `whoami`, and understand the JSON envelope.
- [SDK](https://www.socialfetch.dev/docs/sdk.mdx) — official TypeScript SDK guide, including `SocialFetchClient`, `Result`, and `unwrap()`.
- [Capability matrix](https://www.socialfetch.dev/docs/capability-matrix.mdx) — every operation with identifiers, pagination, outcomes, media download, credits, and its SDK method. Generated from OpenAPI, so use it for route selection instead of scanning individual pages.
- [Recipes](https://www.socialfetch.dev/docs/recipes.mdx) — copyable workflows (brand monitoring, transcripts, Ad Library, creator scoring, Reddit research) with credit callouts and SDK examples.
- [Integrations](https://www.socialfetch.dev/docs/integrations.mdx) — MCP for AI clients, n8n verified node, Apify Store Actors, Make custom app, SDK, and REST API connection paths.
- [MCP product page](https://www.socialfetch.dev/mcp) — hosted MCP overview, OAuth, Skills install.
- [MCP integration](https://www.socialfetch.dev/docs/integrations/mcp.mdx) — hosted `/mcp` server, OAuth, Cursor/VS Code/Claude install snippets, 1112 endpoint tools, plus docs_search/docs_read for implementation help.
- [n8n integration](https://www.socialfetch.dev/docs/integrations/n8n.mdx) — install `n8n-nodes-socialfetch`, credentials, and workflow examples.
- [Apify integration](https://www.socialfetch.dev/docs/integrations/apify.mdx) — Store Actors under @social-fetch, PPE billing, dataset export, and quick start.
- [Make integration](https://www.socialfetch.dev/docs/integrations/make.mdx) — custom app modules for Make scenarios, API key credentials, and module catalog.
- [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt) — every documented operation with a direct link to that route's agent-readable markdown page (prefer this over parsing OpenAPI).
- [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt) — per-platform endpoint files generated from OpenAPI (parameters, credits, curls).
- [`/agents.txt`](https://www.socialfetch.dev/agents.txt) — agent crawl/onboarding file with capabilities, auth rules, and allowlist.
- [`/llms.json`](https://www.socialfetch.dev/llms.json) — structured machine-readable operation inventory with parameter names, pagination, outcomes, credits, and SDK mapping.
- [API reference hub](https://www.socialfetch.dev/docs/api.mdx) — human-friendly index of operations with links into generated pages.
- [Errors](https://www.socialfetch.dev/docs/errors.mdx) — shared error envelope and HTTP status guidance.
- [Credits](https://www.socialfetch.dev/docs/credits.mdx) — metering, `402`, and planning batch jobs.
- Outcome semantics such as `found`, `not_found`, and `private` are documented in [Errors](https://www.socialfetch.dev/docs/errors.mdx) and on operation pages when present in the OpenAPI contract.

## Markdown docs convention

- Every docs page has a markdown twin: append **`.mdx`** to the docs pathname (for example `/docs/quickstart` → `/docs/quickstart.mdx`).
- Agents that send `Accept: text/markdown` on `/docs/**` HTML URLs may receive markdown directly (same URL, `Vary: Accept`).
- Published blog posts use the same convention: `/blog/{slug}` → `/blog/{slug}.mdx`, or `Accept: text/markdown` on the HTML URL (`Vary: Accept`).

---
# List Weibo post comments (https://www.socialfetch.dev/docs/api/v1/weibo/posts/postid/comments/get)

## Summary

List the top comments on a Weibo post, about 20, with likes, region and reply counts.

**Tags:** `Weibo`

## HTTP

- **Method:** GET
- **Path:** `/v1/weibo/posts/{postId}/comments`
- **Base URL:** `https://api.socialfetch.dev`

## Capability summary

- **SDK mapping:** `client.weibo.listPostComments({ postId: "5365286204084354" })`
- **Accepted identifiers:** `postId` (path)
- **Pagination:** none
- **Business outcome field:** `data.lookupStatus` with values `found`, `empty`

## Credits

- 1 credit
- Failed requests are free
- Found, empty and not-found answers are all charged

## Authentication

- **`x-api-key`**: API key (`sfk_...`)

## Parameters

### `postId` (path)

- **Required:** yes
- **Constraints:** type `string`; minLength: 1; maxLength: 512
- **Description:** The post's id: its 16 digits (as in m.weibo.cn/detail/5365286204084354), its short code (the last part of weibo.com/1195230310/Rrookh8wG) or a whole post link.

## Responses (status codes)

- **200**: The top comments on a Weibo post.
- **400**: Invalid request
- **401**: Missing or invalid API key
- **402**: Insufficient credits
- **500**: Unexpected or billing error
- **502**: Lookup could not be completed.
- **503**: Service temporarily unavailable; safe to retry with backoff.

## Response body (200)

The top comments on a Weibo post.

### Field outline

- **data** (required) — type `object`. Endpoint-specific response payload.
  - **lookupStatus** (required) — type `string`; enum: found, empty. `empty` when Weibo shows no comments: the post has none, has them turned off, or no post has this id. The post endpoint tells them apart.
  - **comments** (required) — type `array`. The post's top comments, as Weibo ranks them logged out: up to 20. `page.truncated` says whether there are more.
    - _items:_
      - **id** (required) — type `string`. Comment id.
      - **text** (required) — type `string`; nullable. The comment as plain text, with emoji as `[name]`.
      - **createdAt** (required) — type `string`; nullable. When it was posted, ISO 8601 UTC.
      - **region** (required) — type `string`; nullable. The region Weibo shows it was posted from, when shown.
      - **likes** (required) — type `integer`; nullable. Likes. Null on the first replies shown under a comment, which Weibo sends without a like count.
      - **imageUrls** (required) — type `array`. Pictures posted with the comment.
        - _items:_
          - type `string`
      - **author** (required) — type `object`; nullable. Who wrote it; null when Weibo hides the account.
      - **replyCount** (required) — type `integer`; nullable. How many replies the comment has. Pass its `id` as `commentId` to the replies endpoint.
      - **isLikedByAuthor** (required) — type `boolean`; nullable. True when the post's author liked this comment.
      - **replies** (required) — type `array`. The first replies, as Weibo shows them under the comment logged out (up to 2). `replyCount` says how many there are; the replies endpoint returns more.
        - _items:_
  - **page** (required) — type `object`. Pagination state. Weibo shows logged-out visitors the first page of a list, so there is never a next page.
    - **hasMore** (required) — type `boolean`. Whether another page is available.
    - **nextCursor** (required) — type `string`; nullable. Cursor to pass in the next request when more pages exist; null on the last page.
    - **truncated** (required) — type `boolean`. True when the list has more rows than Weibo shows logged out: it stops here before its end.
    - **total** (required) — type `integer`; nullable. How many rows the list has in all, as Weibo counts them.
- **meta** (required) — type `object`. Metadata describing the request and billing outcome.
  - **requestId** (required) — type `string`; minLength: 1. Unique request identifier for tracing this API call.
  - **creditsCharged** (required) — type `integer`; minimum: 0. Credits charged for this request.
  - **version** (required) — type `string`; enum: v1. Public API version that served the response.
  - **stale** (optional) — type `boolean`; enum: true. Present, and `true`, only when the source couldn't be reached and this is the last good answer for the same request instead, up to 24 hours old. Absent on every live answer.
  - **fetchedAt** (optional) — type `string`. When a stale answer (`stale: true`) was originally fetched (ISO 8601, UTC). Absent on every live answer.

### Example JSON (OpenAPI example)

```json
{
  "data": {
    "lookupStatus": "found",
    "comments": [
      {
        "id": "5365287278876193",
        "text": "何老师辛苦了[心]真的 中国文化博大精深 唐诗宋词 慢慢品[鼓掌]慢慢学",
        "createdAt": "2026-11-14T14:47:12.000Z",
        "region": "江苏",
        "likes": 34,
        "imageUrls": [],
        "author": {
          "id": "1851397621",
          "displayName": "古月JH",
          "avatarUrl": "https://wx2.sinaimg.cn/orj480/6e5a15f5ly8fwrj8uprw1j20ro0roq3g.jpg",
          "url": "https://weibo.com/u/1851397621",
          "isVerified": true
        },
        "replyCount": 1,
        "isLikedByAuthor": false,
        "replies": []
      }
    ],
    "page": {
      "hasMore": false,
      "nextCursor": null,
      "truncated": true,
      "total": 942
    }
  },
  "meta": {
    "requestId": "req_01example_weibo_post_comments",
    "creditsCharged": 1,
    "version": "v1"
  }
}
```

### Machine-readable error codes

When an error JSON body is returned, it may include one of these `error.code` values (derived from the OpenAPI schemas for this operation; additional codes may exist at runtime):

- `bad_request`

## Error handling & retries

Interpret HTTP status codes using the descriptions below. Do not assume a JSON body unless the OpenAPI schema defines one for that status.

- **400**: Invalid request **Retry:** Fix the request; retrying the same invalid payload will not help.
- **401**: Missing or invalid API key **Retry:** Fix the API key first; retrying without changes will not help.
- **402**: Insufficient credits **Retry:** Do not retry without resolving billing/credits (retrying the same request will not help).
- **500**: Unexpected or billing error
- **502**: Lookup could not be completed. **Retry:** May be transient; a few retries with backoff are reasonable.
- **503**: Service temporarily unavailable; safe to retry with backoff. **Retry:** Usually safe to retry with exponential backoff and jitter.

### Suggested client defaults

- Send the API key using the `x-api-key` header on every request.
- On `503` (and sometimes `502`), retry with backoff; cap retries and surface a clear error to the user.
- On `402`, surface an actionable billing message rather than blind retries.

## Examples

### TypeScript SDK

```typescript
import { SocialFetchClient } from "@socialfetch/sdk";

const client = new SocialFetchClient({
  apiKey: process.env.SOCIALFETCH_API_KEY!,
});

const result = await client.weibo.listPostComments({
  postId: "5365286204084354",
});

if (!result.ok) {
  console.error(result.error);
} else {
  console.log(result.value.data);
}
```

### Node.js

```javascript
const response = await fetch(
  "https://api.socialfetch.dev/v1/weibo/posts/5365286204084354/comments",
  {
    headers: {
      "x-api-key": "YOUR_API_KEY"
    }
  }
);

const data = await response.json();
console.log(data);
```

### cURL

```bash
curl "https://api.socialfetch.dev/v1/weibo/posts/5365286204084354/comments" \
  -H "x-api-key: YOUR_API_KEY"
```

### Python

```python
import requests

response = requests.get(
    "https://api.socialfetch.dev/v1/weibo/posts/5365286204084354/comments",
    headers={"x-api-key": "YOUR_API_KEY"},
)
data = response.json()
print(data)
```