WeChat Index API

Get a keyword's WeChat Index over the last 30 days, one figure a day. The WeChat Index is WeChat's score of attention across its search, articles, Moments and more, not a count of searches, and is not comparable with Douyin's or Xiaohongshu's; days are calendar days in China time (UTC+8). Up to 1 items a call; $0.1 per call. Errors and timeouts are not charged; an empty result is charged $0.1.

GEThttps://api.dataxapi.com/v1/wechat/index/keywords/history
Also known aswechat indexweixin indexwechat keyword indexwechat keyword popularity trendIn Chinese: 微信指数 API
Price$0.1/ call · Errors and timeouts are not charged
Returns1 a pageeverything in one answer, no paging
When an upstream failsRetried for youon the same route, or a backup route; never charged

Try it

Change a value and the request on the right follows.
Run · $0.1

Sign in to run it; it runs on your own balance. New accounts can try this endpoint free, up to 1 calls.

The first 7 rows of a response recorded 2026-10-29 09:49 UTC for 露营.
composite_index9/29 – 10/5
9/299/3010/110/210/310/410/5
7-day average · composite_index44,085,199
Highest · 10/5 · composite_index52,354,075
Lowest · 9/30 · composite_index35,843,833
As a table
datecomposite_index
2026-09-2938,626,358
2026-09-3035,843,833
2026-10-0138,536,619
2026-10-0243,998,859
2026-10-0351,530,144
2026-10-0447,706,506
2026-10-0552,354,075
curl -G "https://api.dataxapi.com/v1/wechat/index/keywords/history" \
  --data-urlencode "keyword=咖啡" \
  -H "Authorization: Bearer $DATAXAPI_API_KEY"
{
  "code": "ok",
  "request_id": "678d6757-f6b6-4e9d-9159-8f112fd77386",
  "data": {
    "items": [
      {
        "keyword": "露营",
        "points": [
          {
            "date": "2026-09-29T00:00:00.000Z",
            "composite_index": 38626358
          },
          {
            "date": "2026-09-30T00:00:00.000Z",
            "composite_index": 35843833
          },
          {
            "date": "2026-10-01T00:00:00.000Z",
            "composite_index": 38536619
          },
          {
            "date": "2026-10-02T00:00:00.000Z",
            "composite_index": 43998859
          },
          {
            "date": "2026-10-03T00:00:00.000Z",
            "composite_index": 51530144
          },
          {
            "date": "2026-10-04T00:00:00.000Z",
            "composite_index": 47706506
          },
          {
            "date": "2026-10-05T00:00:00.000Z",
            "composite_index": 52354075
          },
          // … 23 more
        ]
      }
    ]
  },
  "page": {
    "next_cursor": null,
    "cursor_expires_at": null,
    "has_more": false,
    "returned": 1
  },
  "warnings": [],
  "meta": {
    "capability": "wechat.index.keywords.history",
    "result_status": "complete",
    "fetched_at": "2026-10-29T09:49:49.000Z",
    "cached": false,
    "replayed": false,
    "unavailable": {
      "points.search_index": "platform",
      "points.notes": "platform",
      "points.impressions": "platform",
      "points.views": "platform",
      "points.engagements": "platform"
    },
    "billing": {
      "amount": "0.1",
      "currency": "USD",
      "balance_after": "9.9"
    }
  }
}

From a response recorded 2026-10-29 09:49 UTC. Names, text and IDs are examples, and so are the links: none is the recorded one (the page shows no one's personal data); the figures are as recorded. Long lists are cut. The request ID, cursor and balance are made up.

Size as sent: 2.4 KB in the standard view (2.4 KB compact, 2.4 KB full).

{
  "code": "ok",
  "request_id": "75bac3e2-3fa9-447e-a0b8-96bd48ded2b4",
  "data": { "items": [] },
  "page": {
    "next_cursor": null,
    "cursor_expires_at": null,
    "has_more": false,
    "returned": 0
  },
  "warnings": [],
  "meta": {
    "capability": "wechat.index.keywords.history",
    "result_status": "empty",
    "fetched_at": "2026-10-29T09:49:49.000Z",
    "cached": false,
    "replayed": false,
    "unavailable": {
      "points.search_index": "platform",
      "points.notes": "platform",
      "points.impressions": "platform",
      "points.views": "platform",
      "points.engagements": "platform"
    },
    "billing": {
      "amount": "0.1",
      "currency": "USD",
      "balance_after": "9.9"
    }
  }
}

From a recording of 2026-10-29 09:49 UTC, edited by hand to show this case. The request ID and balance are made up.

Size as sent: 560 B in the standard view (560 B compact, 560 B full).

This example as a JSON file

curl -G "https://api.dataxapi.com/v1/wechat/index/keywords/history" \
  --data-urlencode "keyword=咖啡" \
  -H "Authorization: Bearer $DATAXAPI_API_KEY"
# pip install dataxapi
from dataxapi import DataXAPI

dx = DataXAPI()  # reads DATAXAPI_API_KEY
result = dx.wechat.index.keywords.history(keyword="咖啡")
print(result["data"]["items"])
// npm i @dataxapi/sdk
import { DataXAPI } from "@dataxapi/sdk";

const dx = new DataXAPI(); // reads DATAXAPI_API_KEY
const result = await dx.wechat.index.keywords.history({ keyword: "咖啡" });
console.log(result.data.items);
dataxapi call wechat.index.keywords.history 'keyword=咖啡'
{
  "mcpServers": {
    "dataxapi": {
      "type": "http",
      "url": "https://api.dataxapi.com/mcp",
      "headers": {
        "Authorization": "Bearer ${DATAXAPI_API_KEY}"
      }
    }
  }
}

Add this to your MCP client, then ask your agent to call wechat.index.keywords.history.

Parameters

keywordtextrequired

One keyword. Example: 咖啡.

viewtext

How much of each item to return. All three cost the same. Values: compact, standard (default), full.

fieldslist of text

Return only these fields. Each by its path, such as author.name.

Known limits

Returned fields

data.items is a list of keyword index history objects. Preview: the structure may change, announced beforehand.

keywordtextcompact

The keyword

pointslist of objectcompact

The figures day by day, one entry a day, oldest first

points[].datetimecompact

The day: a calendar day in China time (UTC+8), written as midnight UTC of its date (8 a.m. that day in China); passed back as since or until it asks for that same day

points[].search_indexintegercompactThe platform has none

Search index of the day: the platform's index of how much the keyword was searched, not a count of searches

points[].composite_indexintegercompact

Composite index of the day: the platform's index of how much attention content about the keyword drew, not a count

On this platform: The day's WeChat Index

points[].notesintegerstandardThe platform has none

Posts about the keyword that day

Show all 12 fields →
points[].impressionsintegerstandardThe platform has none

Times those posts were shown that day

points[].viewsintegerstandardThe platform has none

Times those posts were read that day

points[].engagementsintegerstandardThe platform has none

Engagements with those posts that day

approximatelist of objectcompact

Which numbers of this item are approximate or lower bounds; absent when all are exact

approximate[].fieldtextcompact

Path of the field, such as metrics.views

approximate[].kindtextcompact

Approximate, or a lower boundapproximatelower_bound

Typical size of one item: compact 1.9 KB, standard 1.9 KB, full 1.9 KB (measured on the response recorded 2026-10-29 09:49 UTC).

What this endpoint cannot give

points[].search_indexThe platform has none
points[].notesThe platform has none
points[].impressionsThe platform has none
points[].viewsThe platform has none
points[].engagementsThe platform has none

When you are charged

A result with data$0.1, once per call
An empty result$0.1
Invalid parameters, a failure of ours or of the data source, a timeoutnot charged
CaseCharged
The most one call can cost$0.1 (send X-Max-Price to refuse anything above your own limit)

Prices as read 2026-10-30 14:10 UTC, under price book 6, in effect since 2026-10-29 13:23 UTC; the Playground reads the price in force before a run.

If the object does not exist

A keyword the WeChat Index does not cover returns an empty result, never a not-found error.

Errors

What this endpoint can answer with; codes all endpoints share are on the full list.

HTTPCodeMeaningCharged
400invalid_paramsA parameter is invalidRetry: After a fixNo
402insufficient_balanceThe balance is too lowRetry: After a fixNo
502upstream_failedThe data source failedRetry: YesNo
504timeoutThe data did not arrive in time; retry with the same idempotency keyRetry: YesNo

All error codes →

Questions

How much does the WeChat Index API cost?

$0.1 per call. The most one call can cost is $0.1.

When am I not charged?

Errors and timeouts are not charged; an empty result is charged $0.1.

How many items does one call return, and how do I get the next page?

1 items a page. The page size is the platform's; limit is not accepted. Everything comes in one page; no cursor is issued.

What happens if the object does not exist?

A keyword the WeChat Index does not cover returns an empty result, never a not-found error.

30-day availability

13 days are on record. The share is written here once 14 days are.

It is not a success rate: how single calls went is not in it, and a failed call is not charged either way.

Every endpoint's state now, and each incident with whether anyone was charged: the status page →

All 5 WeChat Search endpoints

WeChat Search endpoints

Use it in your AI

Copy this prompt

Your API key is built in, so there is nothing to configure.

Read https://dataxapi.com/agents.md and set up DataXAPI in this agent. My API key is dx_…; use it for every DataXAPI call.
Sign in to copy it with your key

No account yet? Sign-up takes an email and no card, and a failed call is never charged.

then paste

Paste it into your agent

It reads the page the prompt points to and connects itself.

Your agent
Read https://dataxapi.com/agents.md and set up DataXAPI in this agent. My API key is dx_••••; use it for every DataXAPI call.
DataXAPI connected · 5 tools ready
now try it

Now ask something

Use one of these, or your own words.

Read https://dataxapi.com/apis/wechat/index/keywords/history.md and help me use the DataXAPI endpoint wechat.index.keywords.history (WeChat Index).
Prefer to set it up by hand?
dataxapi setupgives the agents on your machine (Claude Code, Codex, Cursor) the DataXAPI MCP server and the base skill. The key is read from DATAXAPI_API_KEY; none is written into a file.MCP server: https://api.dataxapi.com/mcp. The entry for your client is under MCP in the request examples of this page; then ask your agent to call wechat.index.keywords.history.Other clients →
Ask with this pageSends the Markdown version
Brief for an AIEverything needed to call it, as text
Show the text
Use the DataXAPI endpoint wechat.index.keywords.history (WeChat Index). Get a keyword's WeChat Index over the last 30 days, one figure a day. The WeChat Index is WeChat's score of attention across its search, articles, Moments and more, not a count of searches, and is not comparable with Douyin's or Xiaohongshu's; days are calendar days in China time (UTC+8).
Call GET https://api.dataxapi.com/v1/wechat/index/keywords/history with the header "Authorization: Bearer $DATAXAPI_API_KEY". Read the key from the environment variable DATAXAPI_API_KEY; never write it into code.
Parameters:
- keyword (required): One keyword. Example: 咖啡.
- view: How much of each item to return. All three cost the same. Values: compact, standard (default), full.
- fields: Return only these fields. Each by its path, such as author.name.
Price: $0.1 per call. Errors and timeouts are not charged; an empty result is charged $0.1.
The answer is JSON: data.items holds keyword index history; meta.billing.amount is what this call was charged.
Example:
curl -G "https://api.dataxapi.com/v1/wechat/index/keywords/history" \
  --data-urlencode "keyword=咖啡" \
  -H "Authorization: Bearer $DATAXAPI_API_KEY"
Full reference in Markdown: https://dataxapi.com/apis/wechat/index/keywords/history.md

Names and identifiers

In Chinese
微信指数 API
Endpoint ID
wechat.index.keywords.history
Endpoint
GET /v1/wechat/index/keywords/history
Last checked 2026-10-30 14:10 UTC.View the Markdown versionopenapi.jsonllms.txt

Start with one key.

224 endpoints on 21 platforms, from $0.0003 a call. Errors and timeouts are not charged.

Start free