WeChat Index · Rankings & trends
Keyword trend (30-day WeChat Index)
Send keywords; get one record per keyword with the 30-day WeChat Index daily series plus latest, average and peak values.
POST/v1/wechat-index/trend
$0.1196per record
- a record, minimum counted
- ≈ $0.142937
- 1,000 records
- ≈ $142.937
- minimum per record fetched
- $0.142937
Paid balance onlyOne request, no cursor
Send it
POST with a JSON body, or GET with the same parameters in the query string. Your key goes in the Authorization header.
curl -X POST "https://api.silklinedata.com/v1/wechat-index/trend" \
-H "Authorization: Bearer $SILKLINE_KEY" \
-H "Content-Type: application/json" \
-d '{"limit":5,"keywords":["咖啡","瑞幸"]}'import os, requests
response = requests.post(
"https://api.silklinedata.com/v1/wechat-index/trend",
headers={"Authorization": "Bearer " + os.environ["SILKLINE_KEY"]},
json={
"limit": 5,
"keywords": ["咖啡", "瑞幸"],
},
)
answer = response.json()
print(answer["data"], answer["meta"]["charged_usd"])const response = await fetch("https://api.silklinedata.com/v1/wechat-index/trend", {
method: "POST",
headers: { Authorization: `Bearer ${process.env.SILKLINE_KEY}`, "Content-Type": "application/json" },
body: JSON.stringify({
"limit": 5,
"keywords": [
"咖啡",
"瑞幸"
]
}),
});
const { data, cursor, meta } = await response.json();
console.log(data, meta.charged_usd);What comes back
Records from a real request on 2026-11-09. Names, avatars and profile links of ordinary users show as <masked>; long text is cut here, not in the API.
{
"data": [
{
"type": "trend",
"keyword": "咖啡",
"dataPointCount": 30,
"startDate": "2026-10-10",
"endDate": "2026-11-08",
"latestIndex": 107331742,
"averageIndex": 97494791,
"peakIndex": 113691075,
"peakDate": "2026-11-06",
"dataPoints": [
{
"date": "2026-10-10",
"timestamp": 1791561600,
"index": 92063363
},
{
"date": "2026-10-11",
"timestamp": 1791648000,
"index": 106041903
},
{
"date": "2026-10-12",
"timestamp": 1791734400,
"index": 99872644
}
]
},
{
"type": "trend",
"keyword": "瑞幸",
"dataPointCount": 30,
"startDate": "2026-10-10",
"endDate": "2026-11-08",
"latestIndex": 38022738,
"averageIndex": 36331868,
"peakIndex": 44248464,
"peakDate": "2026-11-02",
"dataPoints": [
{
"date": "2026-10-10",
"timestamp": 1791561600,
"index": 35362580
},
{
"date": "2026-10-11",
"timestamp": 1791648000,
"index": 38774283
},
{
"date": "2026-10-12",
"timestamp": 1791734400,
"index": 39703628
}
]
}
],
"cursor": null,
"meta": {
"request_id": "req_01JD8Q…",
"charged_usd": "0.285874",
"balance_usd": "9.875000",
"items": 2
}
}Fields 10
| Field | Type | Example value |
|---|---|---|
| type | string | trend |
| keyword | string | 咖啡 |
| dataPointCount | number | 30 |
| startDate | string | 2026-10-10 |
| endDate | string | 2026-11-08 |
| latestIndex | number | 107331742 |
| averageIndex | number | 97494791 |
| peakIndex | number | 113691075 |
| peakDate | string | 2026-11-06 |
| dataPoints | array | [{"date":"2026-10-10","timestamp":1791561600,"index":9206336… |
Parameters 2
| Name | Type | Required | Description | Example |
|---|---|---|---|---|
| limit | integer | no | How many records to return, 1 to 100. A request never returns more than this. | 5 |
| keywords | array | yes | Keywords to look up, Chinese works best (for example 咖啡 or 新能源汽车). One record per keyword, in the order given. Leave it empty to use 咖啡 (coffee). | ["咖啡","瑞幸"] |
Paging
This endpoint answers in one request: raise limit (up to 100) for more records. cursor is always null.
What a request costs
You pay per record; when a request returns few records or none, it is charged at most the endpoint minimum for each page it reads, possibly less, and errors or timeouts on our side are not charged.
Here each record is fetched on its own; the minimum is $0.142937 for each.
- 1 record: up to $0.142937
- 20 records: up to $2.85874
- 100 records: up to $14.2937
The response's meta says what was charged (charged_usd) and what is left (balance_usd). Errors on our side are not charged.
Questions
What parameters does Keyword trend (30-day WeChat Index) take?
Required: keywords. Every request also takes limit (1 to 100).
How many records does one request return?
Up to 100 (limit 1 to 100). A page holds up to 1 records, so 100 records take 100 pages in one request.
Can I page through more results?
No. This endpoint answers in full in one request; the answer's cursor is null.
How much does it cost?
Per record: record $0.1196. The minimum is $0.142937 per page: with few records or none, a request pays at most that for each page it reads, possibly less. 100 records cost at most $14.2937.
What does a request cost when it fails or comes back empty?
You pay per record; when a request returns few records or none, it is charged at most the endpoint minimum for each page it reads, possibly less, and errors or timeouts on our side are not charged. Each answer's meta says what the request was charged and the balance left.