WeChat Official Accounts Article search 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.

POST

API health

24h health: 97%
24h average time: 36.01 s

Healthy / normal
Available
Limited
Mostly down

Healthy

Last 24 hours

Last 30 days

Find WeChat Official Account articles on a topic, up to 400 per call, with title, summary, cover image, account name and publish time. Full article text is not included, and the followed and recently read sections of category are not guaranteed because no personal WeChat sign-in is passed.

WeChat Official Account article search finds articles from public WeChat accounts by keyword and returns each article's title, summary, link, cover image, account name and publish time. Use it to see which articles cover a topic and who writes them: industry news monitoring, collecting public opinion, finding accounts to partner with, or building a topic library.

Pick a section with category: ALL, LATEST or HOT. FOLLOWED and RECENT_READ depend on a personal sign-in, and no WeChat sign-in is passed here, so they are not guaranteed to work and never read your own follows or reading history. posted_at is a standard timestamp while relative_time is a relative phrase as WeChat displays it, so sort by the former. Open url to read the full article.

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 search endpoint (wechat_oa/article_search).

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_search, and put the parameters inside params.
- Required parameters:
  - keyword: Specifies the search term across WeChat Official Account actions, including searching articles (article_search), accounts (account_search), mini programs (mini_program_search), search auto-suggestions (search_suggestions…
- Optional parameters:
  - category: Filters articles by category in the article_search action. Allowed values are ALL, LATEST, HOT, FOLLOWED, and RECENT_READ. Note that FOLLOWED and RECENT_READ depend on account state.
  - sub_type: A compatibility alias for category in article_search that accepts the same five category values (automatically converted to uppercase). If both category and sub_type are provided, category takes precedence.
  - limit: The most rows to return in this call, an integer from 1 to 400. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, title, summary (Article summary shown in the search res…), url, cover_image_url (Cover image URL of the article), account_name (Name of the Official Account that publi…), posted_at, relative_time (Relative time as WeChat displays it (su…), kind (Result type as WeChat labels it).
- Example request body:
{
  "platform": "wechat_oa",
  "action": "article_search",
  "params": {
    "keyword": "城市更新"
  }
}
- 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_search`	Capability identifier, fixed value.
`keyword`	body.params	Not declared	Yes	-	Specifies the search term across WeChat Official Account actions, including searching articles (article_search), accounts (account_search), mini programs (mini_program_search), search auto-suggestions (search_suggestions), and trend indices (wechat_index). It does not search personal WeChat chats.
`category`	body.params	Not declared	No	-	Filters articles by category in the article_search action. Allowed values are ALL, LATEST, HOT, FOLLOWED, and RECENT_READ. Note that FOLLOWED and RECENT_READ depend on account state; because your personal WeChat login session is not passed, these options are not guaranteed to work and will not read your personal subscription or reading history.
`sub_type`	body.params	Not declared	No	-	A compatibility alias for category in article_search that accepts the same five category values (automatically converted to uppercase). If both category and sub_type are provided, category takes precedence.
`limit`	body.params	`integer (1–400)`	No	`20`	The most rows to return in this call, an integer from 1 to 400. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

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": "article_search",
  "params": {
    "keyword": "城市更新"
  }
}'

[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": "article_search",
  "results": [
    {
      "id": …,
      "title": …,
      "summary": …,
      "url": …,
      "cover_image_url": …,
      "account_name": …,
      "posted_at": …,
      "relative_time": …,
      "kind": …,
      "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.
`title`	Title. null when the platform has no titles (for example text-only posts).
`summary`	Article summary shown in the search result.
`url`	Link to the record on the platform.
`cover_image_url`	Cover image URL of the article.
`account_name`	Name of the Official Account that published the article.
`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.
`relative_time`	Relative time as WeChat displays it (such as 3 days ago); sort by posted_at instead.
`kind`	Result type as WeChat labels it.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

FAQ

Which `category` should I use?

ALL, LATEST and HOT cover most needs. FOLLOWED and RECENT_READ depend on a personal WeChat sign-in, which is not passed here, so they are not guaranteed to work. sub_type is an older name for the same setting; when both are sent, category wins.

Is this the same as searching inside WeChat?

It searches Official Account articles, not personal chats or Moments, and it never reads your own follows or reading history. Result order depends on the section you pick and may differ from what you see when you search on your own phone.

Can I pass a result's `url` to the comment or metrics capabilities?

Not always. Search results mostly carry temporary links with signature and timestamp parameters, and the article comment, reply and metrics capabilities answer 422 before any charge when they cannot read one. Open the article in a browser, copy its own link, a /s/ short link or one with __biz, mid, idx and sn, and pass that instead.

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).