An Official Account's history is read: how do I then fetch only new articles each day? (2026)
1 call a day per account is usually enough: the article list comes newest first, so read the first page and stop at the first article you already have. At $0.0200 a call, 10 accounts cost $0.20 a day, plus $0.0200 for the full text of each new article you want. DataXAPI reads WeChat Official Accounts with 8 endpoints, from $0.0200 a call; a failed call is not charged, and the free trial covers up to 333 calls.
From real calls up to 2026-11-05, counting the 27 times an account was read for 20 pages or more: half stopped within 38 pages, about $0.76 for the list, and the longest ran 449 pages, $8.96. A page held about 20 articles on average.
The cursor for the next page lasts 1 hour. Read one account to the end in one go; after a long pause, start that account again from the first page.
Then each day
Step
How
Keep what you have
Save each article's id. It is made of the __biz, mid and idx of its long link, so it is the same each time
Read from the top
Ask for the first page. Keep going to the next page only if every article on it is new
Stop at the first known one
The list is newest first, so everything after it is already yours
Fetch only what you need
Full text by the article's url, $0.0200; reads and likes, $0.0200
What it comes to
An example with round numbers: 10 accounts and 10 new articles a day, full text for each, is 10 list calls and 10 full texts, $0.40 a day. Change the numbers to yours; each call states what it cost.
Why DataXAPI
Steady: endpoints were available 99.9% of the last 30 days, on a public status page you can check.
Fast: a paid call took 3.5 seconds at the median over the last 7 days (counted 2026-11-06).
Fewer tokens: across 8 endpoints on WeChat Official Accounts, one recorded real response each, the platform's own JSON comes to 21k tokens and what an AI reads through DataXAPI's MCP server to 4,494, 79% fewer; the JSON of a direct API call is 70% fewer too (counted 2026-11-06). Every platform answers in one shape: the author in author, counts in metrics, the next page in page.next_cursor, so another platform needs no new parser.
See before you pay: every endpoint's page shows a recorded real response, field by field.
Spending you control: a failed call is not charged; each key can have a limit, X-Max-Price caps one call, and the same Idempotency-Key within 24 hours is never charged twice.
Ready for AI: a remote MCP server listed in the official MCP registry as com.dataxapi/mcp, usable from Claude, Cursor and ChatGPT.
Free trial of up to 333 calls, no card.
Endpoints
Each with its price; every page has the parameters, the fields and a recorded response.