# WeChat Official Accounts Comment replies API (wechat_oa.comment_replies)

- Canonical page: [https://everyinfra.com/en/wechat-oa-api/comment_replies](https://everyinfra.com/en/wechat-oa-api/comment_replies?utm_medium=ai_doc&utm_campaign=page_md)
- Endpoint: POST https://api.everyinfra.com/api/v1/social with {"platform": "wechat_oa", "action": "comment_replies", "params": {...}}
- Price: $0.006764 per call ($6.76 per 1,000 requests); failed calls and empty results are not charged
- Returns: list
- Mode: sync; add "mode": "async" for slow tasks

WeChat Official Account Comment replies reads the replies under one comment on an article, given the article's `url` and the comment's `comment_id`. Every reply comes with its full text, the replier's nickname and avatar, its like count and time, and the country, province and city displayed with it. Use it to follow a thread to the end: who answered a complaint, how readers argued with each other, or which follow-up questions a statement raised.

The comment ID comes from the WeChat Article comments capability, and it only works together with the article link it came from. Location values are passed through as the platform gives them: `country` mixes full names and ISO codes, and `city` keeps the platform's original wording, so normalize both before you group replies by place.

## Health

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

## Parameters

| name | type | required | default | description |
|---|---|---|---|---|
| url | not declared | yes | not declared | Specifies the article's own mp.weixin.qq.com link for article_comments, comment_replies, article_metrics, and article_detail: open the article and copy it (a /s/<id> short link, or a link with __biz, mid, idx, and sn). Temporary links copied from search results (with signature/timestamp) may not be readable; when they cannot be read, the call returns 422 before any charge. Account-level actions accept this parameter only as a lowest-priority fallback input for resolving the target account. |
| comment_id | not declared | yes | not declared | Specifies the target comment ID for comment_replies. Obtain this value from the article_comments response for the same article. Must be paired with the corresponding article URL; this is not an article ID. |
| content_id | not declared | no | not declared | A compatibility alias for comment_id in the comment_replies action. It takes lower precedence than comment_id when both are provided. |
| limit | integer (1–) | no | not declared | The most rows to return in this call, an integer of 1 or more. The default applies when you leave it out, and a call can return fewer rows. |

## Response fields (items in `results`)

| field | meaning |
|---|---|
| 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). |
| author_name | Author's display name. |
| author_avatar_url | platform-native meaning |
| like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
| 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. |
| country | Country or region: a full name or an ISO code depending on the platform, not normalized. |
| province | platform-native meaning |
| city | City name in the platform's language, not normalized. |
| platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |

## 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": "wechat_oa",
  "action": "comment_replies",
  "params": {
    "url": "https://mp.weixin.qq.com/s?__biz=MzA4MTg0MjA5OQ==&mid=2655362972&idx=1&sn=b56fabd8e4c53259498100f05f20dbb0",
    "comment_id": "11658531443289621226"
  }
}'
```

```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": "wechat_oa",
        "action": "comment_replies",
        "params": {
            "url": "https://mp.weixin.qq.com/s?__biz=MzA4MTg0MjA5OQ==&mid=2655362972&idx=1&sn=b56fabd8e4c53259498100f05f20dbb0",
            "comment_id": "11658531443289621226",
        },
    },
    timeout=120,
)
print(response.status_code)
print(response.json())
```

## Response example

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

```text
{
  "id": "req_…",
  "platform": "wechat_oa",
  "action": "comment_replies",
  "results": [
    {
      "id": 2,
      "text": "我也有过，刚高中毕业的时候，什么也不懂，被同班男生问为什么不刮，同时他也收获了我的白眼🙄",
      "author_name": "咩•••凉",
      "author_avatar_url": "https://wx.qlogo.cn/•••",
      "like_count": 70,
      "posted_at": "2026-07-31T04:05:06+00:00",
      "country": "中国",
      "province": "山东",
      "platform": "wechat_oa"
    },
    {
      "id": 5,
      "text": "+1，被人提醒刮腋毛，真的很冒昧",
      "author_name": "小•••）",
      "author_avatar_url": "https://wx.qlogo.cn/•••",
      "like_count": 516,
      "posted_at": "2026-07-31T04:07:41+00:00",
      "country": "中国",
      "province": "广东",
      "platform": "wechat_oa"
    }
  ],
  "count": 4,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}
```

## FAQ

### Where do I get `comment_id`?

Call WeChat Article comments on the same article first. Each comment row has an `id`; pass that value as `comment_id`, together with the identical article `url`. Rows that report replies are the ones worth expanding. An article ID, or a comment ID taken from a different article, does not match the link and will not work.

### Should I send `comment_id` as a number or a string?

As a string. Comment IDs are long, like the 20-digit value in the example on this page, and many JSON parsers and JavaScript round integers that large, which quietly turns one ID into another. Keep them as text everywhere you store or pass them.

### What is `content_id`?

A legacy alias of `comment_id`, still accepted so existing integrations keep working. When a request carries both, `comment_id` takes precedence, so new code should send only `comment_id` and leave `content_id` out.

## Also

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