WeChat · Content details

Channels video details

Send video share links, export IDs or object IDs; get one record per Channels video with description, duration, likes, comments, forwards and author username.

POST/v1/wechat/channelVideoDetails

$0.0184per record

1,000 records
≈ $18.40
minimum per record fetched
$0.012569

Paid balance onlyOne request, no cursor

Try it in the console

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/channelVideoDetails" \
  -H "Authorization: Bearer $SILKLINE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"limit":5,"videos":["export/UzFfBgAAxJurHDpkaUmjk8zT4DCKJapoV2WEDiHj8BmqwpwCqA"]}'

What comes back

Records from a real request on 2026-11-21. Names, avatars and profile links of ordinary users show as <masked>; long text is cut here, not in the API.

200 OK · fetched 2026-11-21
{
  "data": [
    {
      "type": "channelVideoDetail",
      "channelVideoId": "15027469822459579471",
      "exportId": null,
      "title": "地道的老北京小吃炸松肉,自己做一点都…",
      "authorName": "<masked>",
      "authorUsername": "<masked>",
      "authorAvatar": "<masked>",
      "durationSeconds": 172,
      "likeCount": 1446,
      "commentCount": 123,
      "favoriteCount": 2061,
      "forwardCount": 5886,
      "publishedAt": "2026-10-07T23:00:01Z",
      "width": 1080,
      "height": 1920,
      "coverUrl": "https://wxapp.tc.qq.com/251/20304/sto…",
      "ipLocation": "<masked>"
    }
  ],
  "cursor": null,
  "meta": {
    "request_id": "req_01JD8Q…",
    "charged_usd": "0.018400",
    "balance_usd": "9.875000",
    "items": 1
  }
}

Fields 17

FieldTypeExample value
typestringchannelVideoDetail
channelVideoIdstring15027469822459579471
exportIdnullnull
titlestring地道的老北京小吃炸松肉,自己做一点都不费事,外酥里嫩,咬一口满满的牛肉馅太香了!#炸松肉#豆腐皮#老北京小吃#清真小吃
authorNamestring<masked>
authorUsernamestring<masked>
authorAvatarstring<masked>
durationSecondsnumber172
likeCountnumber1446
commentCountnumber123
favoriteCountnumber2061
forwardCountnumber5886
publishedAtstring2026-10-07T23:00:01Z
widthnumber1080
heightnumber1920
coverUrlstringhttps://wxapp.tc.qq.com/251/20304/stodownload?encfilekey=KGD…
ipLocationstring<masked>

Parameters 2

NameTypeRequiredDescriptionExample
limitintegernoHow many records to return, 1 to 100. A request never returns more than this.5
videosarrayyesShare links (https://weixin.qq.com/sph/...), export IDs (export/..., they expire quickly) or numeric object IDs. The IDs of videos found by keyword search are not object IDs: use their exportId.["export/UzFfBgAAxJurHDpkaUmjk8zT4DCKJap…

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.012569 for each.

  • 1 record: up to $0.0184
  • 20 records: up to $0.368
  • 100 records: up to $1.84

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 Channels video details take?

Required: videos. 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: detail record $0.0184. The minimum is $0.012569 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 $1.84.

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.