WeChat Official Accounts Comment replies API

Q: 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.

Temporarily unavailable

We are restoring this capability. Until then calls usually fail or return no results; failed calls and empty results are not charged.

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

List the replies under one comment on a WeChat Official Account article, each with text, replier, likes, time and the country, province and city shown. Pair the comment_id from article comments with that same article's link; replies outside this comment are not rebuilt.

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.

Price $5.56 per 1,000 requests ($0.005556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra WeChat Official Accounts Comment replies endpoint (wechat_oa/comment_replies).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to wechat_oa and action to comment_replies, and put the parameters inside params.
- Required parameters:
- url: 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).
- comment_id: 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.
- Optional parameters:
- content_id: A compatibility alias for comment_id in the comment_replies action. It takes lower precedence than comment_id when both are provided.
- limit: 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.
- Returns a list of records. Main fields of each record: id, text, author_name, author_avatar_url, like_count, posted_at, country, province, city.
- Example request body:
{
"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"
}
}
- Price: $5.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`wechat_oa`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`comment_replies`	Capability identifier, fixed value.
`url`	body.params	Not declared	Yes	-	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`	body.params	Not declared	Yes	-	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`	body.params	Not declared	No	-	A compatibility alias for comment_id in the comment_replies action. It takes lower precedence than comment_id when both are provided.
`limit`	body.params	`integer (1–)`	No	-	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.

Code samples

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"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.

json

{
  "id": "req_…",
  "platform": "wechat_oa",
  "action": "comment_replies",
  "results": [
    {
      "id": …,
      "text": …,
      "author_name": …,
      "author_avatar_url": …,
      "like_count": …,
      "posted_at": …,
      "country": …,
      "province": …,
      "city": …,
      "platform": …
    }
  ],
  "count": …,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

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`	Keeps the platform's own 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`	Keeps the platform's own 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).

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.

Errors and billing

401: Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422: Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402: Insufficient balance. Top up first.
429: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503: Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty: The request completed without data and is not charged (billing.reason = empty_result_refunded).

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

WeChat Official Accounts: Existing Replies and Comment Management Operations ↗
WeChat lists viewing comments, posting replies, deleting replies, and managing featured comments as separate operations. The `comment_replies` endpoint here reads existing replies only and does not grant capabilities to post, delete, or manage comments simply because its name includes replies.
Checked 2026-09-04