ONEAPI / wechat-channels

WeChat Channels API

Build content workflows around WeChat Channels videos and accounts. The Wechat-Channels-V2 docs cover details, creator posts, comments, collections and live content. Media links and decryption keys must be handled as a pair from the same response.

01 / CAPABILITIES

Available capabilities

Video details and media

Retrieve video details, including the media and decode_key information described in the docs.

Endpoint documentation →

Creator video lists

Read an account’s videos; profile information and statistics have separate endpoints.

Endpoint documentation →

Comments and collections

Retrieve video comments, with dedicated documentation for collections and collection videos.

Endpoint documentation →

02 / USE CASES

What you can build

Channels content organization

Combine creator video lists and details to organize videos and collection information.

Media processing workflows

Follow the media-link and decode_key documentation to connect download and decryption steps.

03 / REQUEST EXAMPLE

Retrieve a Channels video by object_id

Replace YOUR_OBJECT_ID with a real object identifier. The docs accept object_id, export_id or share_url, in that priority order, and recommend a 30-second client timeout.

cURLPOST · JSON
curl --request POST 'https://api.getoneapi.com/api/wechat-channels-v2/fetch_video_detail' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
  "object_id" : "YOUR_OBJECT_ID",
  "export_id" : "",
  "object_nonce_id" : "",
  "share_url" : "",
  "raw" : false
}'

Replace YOUR_API_KEY and the content placeholders with real values. This example uses cURL shell syntax; the Apifox docs provide Windows, Python and other examples. Live requests are billed according to your account configuration.

View full parameters and response documentation →

04 / FAQ

Frequently asked questions

Why might a downloaded media URL not play directly?

Channels media may be encrypted. Follow the docs to combine url and url_token, or use full_url, then process the encrypted file with decode_key from the same response.

Can I mix decode_key values from different requests for the same video?

No. Each request may generate a new encrypted link and decode_key. The downloaded file and key must come from the same response to avoid decryption failure.