> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# A WeChat exporter returns ret=200013 freq control. How do I keep collecting articles?

> Keep your existing archive, retrieve a fresh public-account list and add missing articles without rebuilding the collection.

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](https://github.com/wechat-article/wechat-article-exporter/issues/200) 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

1. **Identify the account.** Use the account's verified `gh_…` identifier. If you only have an article link, follow the [article-to-account workflow](/faq/wechat-account-identifier). If you already have an article detail, reuse its `data.content.user_name`.
2. **Retrieve the latest list page.** Call `data:wechat_mp.v2.fetch_account_articles` with the article tab, `raw:false` and an empty `offset`. Authenticate with a BeatAPI API key; the request needs no WeChat backend cookie and no login credentials from the old tool.
3. **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](/guides/read-wechat-article) only for the new articles you need.
4. **Page backward when needed.** Pass the returned `next_offset` to the next request, and use `is_end` to detect the end of the list. Save and export pages with the [account-history workflow](/guides/wechat-account-articles). 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:

```json
{"action":"wechat_mp.v2.fetch_account_articles","params":{"username":"<verified_account_username>","offset":"","item_show_type":0,"raw":false}}
```

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?

| What happened                                             | Next action                                                                                                                     |
| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| The old tool still reports `ret=200013`                   | Keep the archive and use the fresh-list workflow; `ret=200013` is not a BeatAPI HTTP status                                     |
| BeatAPI reports an input, authentication or balance error | Correct the setting identified in the error                                                                                     |
| BeatAPI HTTP 429                                          | Schedule a later request using `Retry-After` when supplied                                                                      |
| Timeout or failed business status                         | Keep the error and the `request_id` when available, review the request record and keep the progress of the last successful page |

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](/guides/wechat-incremental-articles). 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](https://beatapi.io/pricing). Reuse saved lists and article bodies instead of fetching the same material again.

[WeChat questions](/faq/wechat)