WeChat Official Accounts Comment replies API
Read the replies under one comment from the article link url and the comment's comment_id: text, like_count, posted_at, and the replier's country, province and city, for $6.76 per 1,000 calls.
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.
comment_idcomes from thearticle_commentsresult for the same article.- It reads existing replies and does not post replies.
- Failed calls and empty results are not charged.
May be temporarily unavailable at peak times
This capability may be temporarily unavailable at peak times; try again later. Failed calls are not charged.
API health
- 24h health
- Normal
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
1Request
POST /api/v1/social { "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" } }2JSON response
{ "results": [ { "author_name": "咩•••凉", "text": "我也有过,刚高中毕业的时候,什么也不懂,被同班男生问为什么不刮,同时他也收获了我的白眼🙄", "like_count": 70, "posted_at": "2026-07-31T04:05:06+00:00" }, … ], "count": 4 }3Rows
author_name text like_count posted_at 咩•••凉 我也有过,刚高中毕业的时候,什么也不懂,被同班男生问为什么不刮,同时他也收获了我的白眼🙄 70 2026-07-31T04:05:06+00:00 小•••) +1,被人提醒刮腋毛,真的很冒昧 516 2026-07-31T04:07:41+00:00 4CSV
wechat_oa-comment_replies-sample.csv id,text,author_name,author_avatar_url,like_count,posted_at,country,province,city,platform
url and comment_id goes in, and the replies under that comment come back; each row in results is one reply, listed as a field table and a CSV file.What data you get
The table shows a real call for mp.weixin.qq.com/s?__biz=MzA4MTg0MjA5OQ==&mid=2655362972&idx=1&sn=b56fabd8e4c53259498100f05f20dbb0, captured November 7, 2026 at 14:47 (UTC), that returned 4 rows; gray bars mark removed personal information (••• in the CSV). Your own calls return these fields as listed in the field reference.
| id | text | author_name | author_avatar_url | like_count | posted_at | country | province | city | platform |
|---|---|---|---|---|---|---|---|---|---|
2 | 我也有过,刚高中毕业的时候,什么也不懂,被同班男生问为什么不刮,同时他也收获了我的白眼🙄 | 咩•••凉 | 70 | 2026-07-31T04:05:06+00:00 | 中国 | 山东 | null | wechat_oa | |
5 | +1,被人提醒刮腋毛,真的很冒昧 | 小•••) | 516 | 2026-07-31T04:07:41+00:00 | 中国 | 广东 | null | wechat_oa |
Use cases
Read a whole discussion under one comment
Pick a comment in
article_comments, use itsidascomment_id, and read thetextof the replies below it.Find the replies readers back
Sort by
like_countto see which reply under a comment drew the most likes.Look at replies by place
provinceandcityare the province and city shown for the replier, so you can group the replies under one comment by place.
Limits and gotchas
urlandcomment_idare both required, andcomment_idmust belong to the article inurl. It is a comment ID, not an article ID.comment_idis a long string of digits. Send it as a string.content_idis an older name forcomment_idand ranks belowcomment_id.- There is no
is_topand noreply_counthere. Those two are inarticle_comments; this capability addscity. - One call reads the replies under one comment. There is no paging parameter.
Pricing
You pay $0.006764 per call, not per row. Failed calls and empty results are not charged.
| Calls | Cost |
|---|---|
| 10,000 | $67.64 |
| 100,000 | $676.39 |
| 1,000,000 | $6,763.89 |
Totals use the list price per call.
Code samples
#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.
API reference
See the parameters, response fields, errors and billing for comment_replies, and copy the page or open it as Markdown for an AI assistant.
AI prompt
#Please help me write a data collection script with the EveryInfra WeChat Official Accounts Comment replies endpoint (wechat_oa/comment_replies).
How the endpoint works:
- 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: $6.76 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 | string | 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 | string | 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 | string | 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. |
Response example
#{ "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": { … }}
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). |
Errors and billing
#- 401
- Missing or invalid key.
- 402
- Insufficient balance. Top up first.
- 422
- Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
- 429
- Per-minute request limit reached. Wait for Retry-After, then try again.
- 503
- Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
- 200 empty
- No data. No charge.
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
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.
Which fields does Comment replies return?
id, text, author_name, author_avatar_url, like_count, posted_at, country, province and city.
How much does reading the replies of one comment cost?
It costs $0.006764 per call, or $6.76 per 1,000 calls, and one call reads the replies under one comment. Failed calls and empty results are not charged.
Related WeChat Official Accounts endpoints
You can call the other WeChat Official Accounts endpoints with the same EveryInfra API key.
- Article search
article_search$8 per 1,000 callsSearch WeChat Official Account articles by keyword through an English-documented API, up to 400 articles per call. - Article details
article_detail$5.56 per 1,000 callsFetch the full body of one WeChat Official Account article as plain text and original HTML. - Account search
account_search$16 per 1,000 callsLook up WeChat Official Accounts by keyword, up to 400 per call. - Mini Program search
mini_program_search$5.56 per 1,000 callsDiscover WeChat Mini Programs for a keyword, with name, icon, description, username and whether each one is a mini game. - Search suggestions
search_suggestions$5.56 per 1,000 callsGet the autocomplete suggestions WeChat offers for a keyword, along with the number of terms returned. - Account details
account_profile$8 per 1,000 callsGet a WeChat Official Account profile as JSON. - Account owner
account_principal$5.56 per 1,000 callsRead the registered owner behind a WeChat Official Account. - Account articles
account_articles$8 per 1,000 callsPull the article history of one WeChat Official Account, 8 by default and up to 160 per call. - Today's account articles
account_today_articles$8 per 1,000 callsTrack what one WeChat Official Account has published today, with each article's title, link, cover, publish time, position and original or deleted flags. - Article comments
article_comments$6.76 per 1,000 callsCollect reader comments on one WeChat Official Account article, up to 260 per call. - Article engagement
article_metrics$5.56 per 1,000 callsCheck engagement on one WeChat Official Account article. - WeChat Index
wechat_index$5.56 per 1,000 callsGauge how much attention a keyword gets on WeChat: the latest index value and its date, plus the trend series behind it.