WeChat Official Accounts Article comments API
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
- 24h average time
- —
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Collect reader comments on one WeChat Official Account article, up to 260 per call, with text, author, likes, pinned flag, reply count and displayed location. Pass the article's own link rather than an account page; not every comment is guaranteed to come back.
WeChat Official Account Article comments returns the public comments on one article from its url: for each comment, the text in full, who wrote it and their avatar, the likes, when it was posted, whether it is pinned, how many replies it drew, and the country and province shown with it. PR and communications teams use it to see how readers took a press release or a statement, and content teams use it to learn which points readers pick up, question or dispute.
Pass the article's own link on mp.weixin.qq.com, not an account page. is_top marks comments pinned to the top, which readers see first, so keep them apart when you score sentiment. Sorting by like_count shows which reactions other readers endorsed, and replies sit one level down, where the WeChat Comment replies capability reads them.
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 Article comments endpoint (wechat_oa/article_comments).
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 article_comments, 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).
- Optional parameters:
- limit: The most rows to return in this call, an integer from 1 to 260. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 13)
- Returns a list of records. Main fields of each record: id, text, author_name, author_avatar_url, like_count, posted_at, is_top, reply_count, country, province.
- Example request body:
{
"platform": "wechat_oa",
"action": "article_comments",
"params": {
"url": "https://mp.weixin.qq.com/s?__biz=MzA4MTg0MjA5OQ==&mid=2655362972&idx=1&sn=b56fabd8e4c53259498100f05f20dbb0"
}
}
- 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 | article_comments | 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. |
limit | body.params | integer (1–260) | No | 13 | The most rows to return in this call, an integer from 1 to 260. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |
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": "article_comments",
"params": {
"url": "https://mp.weixin.qq.com/s?__biz=MzA4MTg0MjA5OQ==&mid=2655362972&idx=1&sn=b56fabd8e4c53259498100f05f20dbb0"
}
}'[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
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.
{
"id": "req_…",
"platform": "wechat_oa",
"action": "article_comments",
"results": [
{
"id": …,
"text": …,
"author_name": …,
"author_avatar_url": …,
"like_count": …,
"posted_at": …,
"is_top": …,
"reply_count": …,
"country": …,
"province": …,
"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. |
is_top | Keeps the platform's own meaning |
reply_count | Replies, usually replies to a comment. null means not disclosed. |
country | Country or region: a full name or an ISO code depending on the platform, not normalized. |
province | Keeps the platform's own meaning |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
FAQ
Which link does url need?
The article's own address on mp.weixin.qq.com, such as the long form with __biz, mid, idx and sn in the query string that the example on this page uses. An account profile link or a search page does not point at a single article, so it cannot return that article's comments.
How do I get the replies to a comment?
Check reply_count. When it is above zero, pass the same article url and that row's id to the WeChat Comment replies capability, which takes them as the article link and the comment ID. Both must come from the same article, since a comment ID only means something together with its own article link.
What do country and province describe?
The location shown with each comment. country comes back as a full name or an ISO code depending on the source, without normalization, so map both forms to one list before you count comments by country. province gives the region within the country when it is shown.
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: Distinction Between Article Comments and Featured Comments ↗
WeChat comment documentation distinguishes among articles, comment IDs, featured flags, and reply details. The comment scope visible in the backend of official authorized interfaces is not identical to the visibility scope of this endpoint, and `is_top` cannot be directly treated as the official comment_type featured flag.
Checked 2026-09-04