WeChat Channels Comments API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Read the top-level comments on one WeChat Channels video by its numeric ID or share link, up to 25 per page. Each comment has its text, likes, time, the commenter's IP region, name and avatar, plus their Channels account ID when they have one. Page on with next_page_token.

Price $8 per 1,000 requests ($0.008 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

Please help me write a data collection script with the EveryInfra WeChat Channels Comments endpoint (wechat_channels/comments).

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_channels and action to comments, and put the parameters inside params.
- Required parameters:
- object_id: The numeric ID of the WeChat Channels video whose comments you want, such as 15039881603147501275, taken from the id of a user_posts or video row, or the video's share link (https://weixin.qq.com/sph/...).
- Optional parameters:
- page_token: Page token for comments. Leave it out for the first page, then pass back the previous response's next_page_token exactly as received, for the same video. Each page is one call; the last page has no next_page_token.
- Returns a list of records. Main fields of each record: id (Video ID (a digit string) on user_posts…), text, like_count (Likes: the video's on search, user_post…), posted_at, author_username (The author's WeChat Channels account ID…), author_name, author_avatar_url (The commenter's avatar link (comments)), ip_location (The commenter's IP region as Channels d…), next_page_token.
- Example request body:
{
"platform": "wechat_channels",
"action": "comments",
"params": {
"object_id": "15039881603147501275"
}
}
- Price: $8 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_channels`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`comments`	Capability identifier, fixed value.
`object_id`	body.params	`string`	Yes	-	The numeric ID of the WeChat Channels video whose comments you want, such as `15039881603147501275`, taken from the `id` of a `user_posts` or `video` row, or the video's share link (`https://weixin.qq.com/sph/...`).
`page_token`	body.params	`string`	No	-	Page token for `comments`. Leave it out for the first page, then pass back the previous response's `next_page_token` exactly as received, for the same video. Each page is one call; the last page has no `next_page_token`.

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_channels",
  "action": "comments",
  "params": {
    "object_id": "15039881603147501275"
  }
}'

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

Response example

Field preview

No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.

json

{
  "id": "req_…",
  "platform": "wechat_channels",
  "action": "comments",
  "results": [
    {
      "id": …,
      "text": …,
      "like_count": …,
      "posted_at": …,
      "author_username": …,
      "author_name": …,
      "author_avatar_url": …,
      "ip_location": …,
      "next_page_token": …,
      "platform": …
    }
  ],
  "next_page_token": …,
  "pagination": { … },
  "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`	Video ID (a digit string) on user_posts and video rows; pass it as `object_id` to video or comments. On comments, the comment ID.
`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).
`like_count`	Likes: the video's on search, user_posts and video rows, the comment's on comments rows. On user_posts and video, likes above 10,000 are precise only to the hundreds, always ending in 02 (20002 is about 20,000); from 100,000 up it is always 100002 (the app only shows 100k+).
`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.
`author_username`	The author's WeChat Channels account ID, v2_...@finder (user_posts / video); pass it as `username` to user_posts.
`author_name`	Author's display name.
`author_avatar_url`	The commenter's avatar link (comments).
`ip_location`	The commenter's IP region as Channels displays it, in Chinese characters or in English, such as Beijing (comments).
`next_page_token`	Keeps the platform's own meaning
`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.

Errors