ONEAPI / wechat-official-accounts

WeChat Official Accounts API

Look up article body, title, author, cover and publication time from a WeChat article URL, then connect account article lists, engagement data and comments. This overview follows the documented Wechat-MP-V2 series.

01 / CAPABILITIES

Available capabilities

Article details

Use an article URL to retrieve body, title, author, cover, publication time and related information.

Endpoint documentation →

Account article lists

Retrieve an account’s article list and combine it with individual detail lookups.

Endpoint documentation →

Article engagement

Engagement data has a dedicated endpoint, with separate endpoints for article comments and replies.

Endpoint documentation →

02 / USE CASES

What you can build

Article reference libraries

Organize article details by URL and use account article lists to add publications.

Editorial review

Combine article details, engagement data and comments to review topics and reader feedback.

03 / REQUEST EXAMPLE

Retrieve an article using its WeChat URL

Replace YOUR_WECHAT_ARTICLE_URL with a real article URL. The docs recommend a 30-second client timeout; consult the endpoint for raw behavior and response details.

cURLPOST · JSON
curl --request POST 'https://api.getoneapi.com/api/wechat-mp-v2/fetch_mp_article_detail' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
  "url" : "YOUR_WECHAT_ARTICLE_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 is a 30-second client timeout recommended?

The article detail docs note that WeChat may respond slowly and recommend a 30-second timeout. A short timeout can leave a processed or billed request without a response received by the client.

Does article detail include engagement data and every comment?

Do not assume so. Article details, engagement, comments and comment replies have separate documented endpoints and should be combined as needed.