A WeChat exporter returns ret=200013 freq control. How do I keep collecting articles?
When an old exporter returns ret=200013 / freq control, keep the articles you already saved, retrieve a fresh list with wechat_mp.v2.fetch_account_articles and the public account identifier, and add the missing articles. To resume competitor research or update a knowledge base, start with recent publications; you usually do not need to export the entire history again.
Will slowing down or waiting fix it?
Not on the old exporter’s route. The wechat-article-exporter maintainer’s July 30, 2026 notice attributes the project’s shutdown to the closure of the interface the project depended on, so a longer delay gives persistent failures on that route no basis for recovery.
Keep your exported files, the last successful date and the article links: the old exports are still useful for reading and for matching existing records. Treat collecting new material as a separate task from repairing the old tool.
Resume the account collection
- Identify the account. Use the account’s verified
gh_…identifier. If you only have an article link, follow the article-to-account workflow. If you already have an article detail, reuse itsdata.content.user_name. - Retrieve the latest list page. Call
data:wechat_mp.v2.fetch_account_articleswith the article tab,raw:falseand an emptyoffset. Authenticate with a BeatAPI API key; the request needs no WeChat backend cookie and no login credentials from the old tool. - Compare against the archive. Keep the title, link and publication time. Match by article identity to separate existing and new records, and keep distinct links for articles with the same title. Reuse saved bodies, and retrieve text only for the new articles you need.
- Page backward when needed. Pass the returned
next_offsetto the next request, and useis_endto detect the end of the list. Save and export pages with the account-history workflow. Start a fresh cursor chain; do not reuse the old exporter’s page numbers or cursors.
The first list request body for POST /v1/social-data/call is below; replace the account identifier:
For example, your archive covers publications through November 10 and you need the latest week. Compare the new list with the saved records and add the missing articles; continue paging if one page does not reach November 10. Deliver three items: a list of additions, a list of articles that still need text retrieval, and the date range you actually checked.
What if the new request also fails?
Mark a page complete only after the page’s successful list is saved. Keep an empty list distinct from a failed request, and describe “the latest week” with the range you actually checked. When asking for support, share the account, the time, an error summary and the request ID; keep API keys in your own configuration.
For example, the old archive last reached October 31. Start from the first page of the new list and match articles against the old archive. When you reach the October 31 checkpoint, also review the other articles on the same page. If the page limit comes first, record how far you got and fill the gap later. Keep the old tool’s errors and the new workflow’s errors with their own times and request records.
Continue with weekly updates
Use the saved article identities as the baseline for the incremental update workflow. For a weekly run, connect the incremental update workflow to your own scheduler.
List, body and statistics retrieval are billed separately; see the current pricing page. Reuse saved lists and article bodies instead of fetching the same material again.

