WeChat Official Accounts WeChat Index API
Temporarily unavailable
We are restoring this capability. Until then calls usually fail or return no results; failed calls and empty results are not charged.
API health
- 24h health
- 0%
- 24h average time
- —
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Gauge how much attention a keyword gets on WeChat: the latest index value and its date, plus the trend series behind it. It is an index, not a count of searches or unique users, and not an EveryInfra metric.
WeChat Index looks up WeChat's index for one keyword and returns the latest value in latest_index with its date in latest_date, plus the series behind it in trend, where data_points counts the points. It answers how much attention a word, brand or topic gets inside WeChat and which way that attention is moving, for marketers sizing interest in a brand, content teams timing topics and analysts comparing attention before and after a campaign.
The value is an index, so compare a keyword with its own history first: a rise in trend after a launch or a news event says more than any single reading. keyword here only feeds the index; to read the articles behind a spike, run the same word through the WeChat Article search capability.
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 WeChat Index endpoint (wechat_oa/wechat_index).
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 wechat_index, 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…
- Returns one object. Main fields: keyword, latest_index, latest_date, data_points, trend.
- Example request body:
{
"platform": "wechat_oa",
"action": "wechat_index",
"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 | wechat_index | 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. |
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": "wechat_index",
"params": {
"keyword": "科技"
}
}'[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": "wechat_index",
"results": {
"keyword": …,
"latest_index": …,
"latest_date": …,
"data_points": …,
"trend": …,
"platform": …
},
"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 |
|---|---|
keyword | Keeps the platform's own meaning |
latest_index | Keeps the platform's own meaning |
latest_date | Keeps the platform's own meaning |
data_points | Keeps the platform's own meaning |
trend | Keeps the platform's own meaning |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
FAQ
Is the WeChat Index a search volume?
No. It is an index WeChat computes for the keyword, so read it as a relative measure of attention, not as a count of searches, readers or articles. Use it to compare periods and spot turning points, and avoid converting it into an audience size.
How do I read trend?
trend is the series of index values over time, and data_points tells you how many values it holds. latest_index and latest_date give the most recent point on its own, handy for a dashboard figure; chart the full series when you look for peaks and turning points.
How do I compare several keywords?
Call once per keyword, since each call takes a single keyword. Align the series by date before comparing, and check data_points so that series of different lengths are not compared point for point. The WeChat Search suggestions capability shows related phrasings that may deserve a series of their own.
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).