WeChat Official Account article detail API
Get one WeChat Official Account article by its link: title, text, time published, the account's name and IDs. One object a call; $0.0200 per call. Errors, timeouts and objects that do not exist are not charged.
Try it
Change a value and the request on the right follows.Sign in to run it; it runs on your own balance. New accounts can try this endpoint free, up to 5 calls.
Used to call POST /v1/wechat/mp/articles/detail? It is this address now. What changed for old endpoints
curl -G "https://api.dataxapi.com/v1/wechat_mp/articles/get" \ --data-urlencode "url=https://mp.weixin.qq.com/s?__biz=MjM5MjAxNDM4MA==&mid=2667038683&idx=1&sn=0422127e651acd7f6cf6ef7e1cff04bc" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
{
"code": "ok",
"request_id": "ea6d90ba-c743-4de0-b6ee-bf22a76e2d0f",
"data": {
"item": {
"id": "2667741100_1",
"url": "https://mp.weixin.qq.com/s/FeLlyCmjO-KbG27_xPHWlw",
"type": "article",
"title": "周末露营入门指南:一篇讲清楚",
"text": "周末露营这件事,越简单越好",
"published_at": "2026-10-10T09:13:21.000Z",
"author": {
"id": "gh_fd3bca9a4315",
"username": "aya_living",
"name": "认真生活的阿雅",
"avatar_url": "https://wx.qlogo.cn/mmhead/TP60gpehOQj0c0q4rzcuTqqksajtafmfdf2AzWc3/132"
}
}
},
"warnings": [],
"meta": {
"capability": "wechat_mp.articles.get",
"result_status": "complete",
"fetched_at": "2026-10-12T19:03:48.000Z",
"cached": false,
"replayed": false,
"unavailable": {
"lang": "capability",
"author.verified": "capability",
"author.followers": "capability",
"metrics": "capability",
"images": "capability",
"hashtags": "platform",
"mentions": "platform",
"is_pinned": "capability",
"post_id": "platform",
"parent_id": "platform",
"root_id": "platform"
},
"billing": {
"amount": "0.02",
"currency": "USD",
"balance_after": "9.98"
}
}
}From a response recorded 2026-10-12 19:03 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.9 KB in the standard view (2.4 KB compact, 2.9 KB full).
curl -G "https://api.dataxapi.com/v1/wechat_mp/articles/get" \ --data-urlencode "url=https://mp.weixin.qq.com/s?__biz=MjM5MjAxNDM4MA==&mid=2667038683&idx=1&sn=0422127e651acd7f6cf6ef7e1cff04bc" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
from dataxapi import DataXAPI dx = DataXAPI() # reads DATAXAPI_API_KEY result = dx.wechat_mp.articles.get(url="https://mp.weixin.qq.com/s?__biz=MjM5MjAxNDM4MA==&mid=2667038683&idx=1&sn=0422127e651acd7f6cf6ef7e1cff04bc") print(result["data"]["item"])
import { DataXAPI } from "@dataxapi/sdk";
const dx = new DataXAPI(); // reads DATAXAPI_API_KEY
const result = await dx.wechat_mp.articles.get({ url: "https://mp.weixin.qq.com/s?__biz=MjM5MjAxNDM4MA==&mid=2667038683&idx=1&sn=0422127e651acd7f6cf6ef7e1cff04bc" });
console.log(result.data.item);dataxapi call wechat_mp.articles.get 'url=https://mp.weixin.qq.com/s?__biz=MjM5MjAxNDM4MA==&mid=2667038683&idx=1&sn=0422127e651acd7f6cf6ef7e1cff04bc'{
"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_mp.articles.get.
Parameters
Link to the article: the long link with __biz, mid, idx and sn, or the short /s/ link. Example: https://mp.weixin.qq.com/s?__biz=MjM5MjAxNDM4MA==&mid=2667038683&idx=1&sn=0422127e651acd7f6cf6ef7e1cff04bc. Full link: https://mp.weixin.qq.com/s?__biz=MjM5MjAxNDM4MA==&mid=2667038683&idx=1&sn=0422127e651acd7f6cf6ef7e1cff04bc. Short link: https://mp.weixin.qq.com/s/TSNQKkRpN1qbKsT7BvzqIw. The link has to be opened to learn what it points at, so the result cannot be checked against it.
How much of each item to return. All three cost the same. Values: compact, standard (default), full.
Return only these fields. Each by its path, such as author.name.
Known limits
- One object per call: there is nothing to page.
- 20 fields of the object are not available from this endpoint
Returned fields
data.item is one post object. Stable: fields are only ever added.
ID; pass it unchanged to the get endpoint
On this platform: Made of the __biz, mid and idx of the article's long link; an article is fetched by its url, not by this
Link that opens the post
Content formatvideoimagetextarticle
Title
Body text
Long text: the compact view keeps the first 500 characters and says so in warnings.
Language of the text
Show all 34 fields →
When it was published
Author
Author's account ID
Author's handle
Author's display name
Author's avatar
Whether the author is verified
Author's follower count
Engagement counts
Likes
Comments
Shares
Saves
Views
Reposts
Image addresses
Hashtags, without the #
Accounts mentioned in the text
Account ID
Handle
Display name
Whether the author pinned it
ID of the thread's root post when this is a reply; otherwise null
ID of the item it replies to directly; otherwise null
ID of the first-level reply its thread hangs under
Which numbers of this item are approximate or lower bounds; absent when all are exact
Path of the field, such as metrics.views
Approximate, or a lower boundapproximatelower_bound
Typical size of one item: compact 1.7 KB, standard 2.3 KB, full 2.3 KB (measured on the response recorded 2026-10-12 19:03 UTC).
What this endpoint cannot give
langNot provided hereauthor.verifiedNot provided hereauthor.followersNot provided heremetricsNot provided heremetrics.likesNot provided heremetrics.commentsNot provided heremetrics.sharesNot provided heremetrics.favoritesNot provided heremetrics.viewsNot provided heremetrics.repostsNot provided hereimagesNot provided herehashtagsThe platform has nonementionsThe platform has nonementions[].idThe platform has nonementions[].usernameThe platform has nonementions[].nameThe platform has noneis_pinnedNot provided herepost_idThe platform has noneparent_idThe platform has noneroot_idThe platform has noneWhen you are charged
X-Max-Price to refuse anything above your own limit)Prices as read 2026-10-21 09:10 UTC, under price book 2, in effect since 2026-10-17 11:00 UTC; the Playground reads the price in force before a run.
If the object does not exist
The answer is 404 not_found and nothing is charged. reason says which: not_found (it does not exist) or private_or_deleted.
Errors
What this endpoint can answer with; codes all endpoints share are on the full list.
invalid_paramsA parameter is invalidRetry: After a fixNoinsufficient_balanceThe balance is too lowRetry: After a fixNonot_foundThe object does not exist, is private or was deletedRetry: NoNoupstream_failedThe data source failedRetry: YesNotimeoutThe data did not arrive in time; retry with the same idempotency keyRetry: YesNoQuestions
How much does the WeChat Official Account article detail API cost?
$0.0200 per call. The most one call can cost is $0.0200.
When am I not charged?
Errors, timeouts and objects that do not exist are not charged.
What happens if the object does not exist?
The answer is 404 not_found and nothing is charged. reason says which: not_found (it does not exist) or private_or_deleted.
The same thing on other platforms
All 6 WeChat Official Accounts endpoints
Use it in your AI
Copy this prompt
Your API key is built in, so there is nothing to configure.
No account yet? Sign-up takes an email and no card, and a failed call is never charged.
Paste it into your agent
It reads the page the prompt points to and connects itself.
Now ask something
Use one of these, or your own words.
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_mp.articles.get.Other clients →Show the text
Use the DataXAPI endpoint wechat_mp.articles.get (WeChat Official Account article detail). Get one WeChat Official Account article by its link: title, text, time published, the account's name and IDs. Call GET https://api.dataxapi.com/v1/wechat_mp/articles/get with the header "Authorization: Bearer $DATAXAPI_API_KEY". Read the key from the environment variable DATAXAPI_API_KEY; never write it into code. Parameters: - url (required): Link to the article: the long link with __biz, mid, idx and sn, or the short /s/ link. Example: https://mp.weixin.qq.com/s?__biz=MjM5MjAxNDM4MA==&mid=2667038683&idx=1&sn=0422127e651acd7f6cf6ef7e1cff04bc. Full link: https://mp.weixin.qq.com/s?__biz=MjM5MjAxNDM4MA==&mid=2667038683&idx=1&sn=0422127e651acd7f6cf6ef7e1cff04bc. Short link: https://mp.weixin.qq.com/s/TSNQKkRpN1qbKsT7BvzqIw. The link has to be opened to learn what it points at, so the result cannot be checked against it. - 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.0200 per call. Errors, timeouts and objects that do not exist are not charged. The answer is JSON: data.item holds post; meta.billing.amount is what this call was charged. Example: curl -G "https://api.dataxapi.com/v1/wechat_mp/articles/get" \ --data-urlencode "url=https://mp.weixin.qq.com/s?__biz=MjM5MjAxNDM4MA==&mid=2667038683&idx=1&sn=0422127e651acd7f6cf6ef7e1cff04bc" \ -H "Authorization: Bearer $DATAXAPI_API_KEY" Full reference in Markdown: https://dataxapi.com/apis/wechat_mp/articles/get.md
Names and identifiers
- In Chinese
- 微信公众号文章详情 API
- Endpoint ID
wechat_mp.articles.get- Endpoint
GET /v1/wechat_mp/articles/get
Start with one key.
207 endpoints on 21 platforms, from $0.0003 a call. Errors and timeouts are not charged.