[中文]

用途:

传 gh_username，返回公众号历史发文列表。两种翻页方式：

手动翻页（推荐做增量 / 精确控量）：max_pages = 1（默认）取单页 → 从响应里取 next_offset（base64 游标）→ 下次请求把它放进 offset 取下一页；响应 is_end 为真即到末页。

自动翻页：max_pages > 1 —— 自动续拉、跨页按文章 id 去重，一次返回多页合并结果；到末页提前停止。

价格：0.01$/次

⏱️ 由于微信服务器原因，本接口响应较慢，请将客户端请求超时（timeout）设置为 30 秒；timeout 设置过小会造成已扣费但收不到响应的情况。

参数:

username: 公众号 gh_username（gh_…）。示例 gh_363b924965e9

page_size: 可选，默认 20，范围 10-20。每页文章数。

max_pages: 可选，默认 1，范围 1-10。1=单页（配 offset 手动翻页）；>1=自动续拉并合并去重。

offset: 可选，翻页游标（base64），首页留空；手动翻页（max_pages=1）时传上一页响应的 next_offset。示例 CAMQChiS5KfRBiAKOJLkp9EGQABIAVgAYABwAQ==

raw: 可选，默认 True。True=原始；False=精简解析。

公众号文章列表及翻页游标

提示：offset 是 base64 游标（含 +/=），统一走 POST body。自动翻页（max_pages>1）下 offset 一般无需手动传。

响应结构与 JSON Path:

`raw=false`（精简解析，snake_case）:

公众号 username: $.data.biz_username

是否末页（0/1）: $.data.is_end

本次返回文章数: $.data.count

下一页游标（手动翻页回传 offset；末页为 null）: $.data.next_offset

实际拉取页数: $.data.pages

文章列表: $.data.articles[]

单篇（N 为下标）:

文章 appmsgid: $.data.articles[N].app_msg_id

标题: $.data.articles[N].title

摘要: $.data.articles[N].digest

链接: $.data.articles[N].url

封面: $.data.articles[N].cover（多比例 $.data.articles[N].covers）

发布 / 更新时间戳: $.data.articles[N].create_time / .update_time

群发内位置 / 类型: $.data.articles[N].idx / .msg_type / .item_show_type

图文数 / 付费标志: $.data.articles[N].pic_count / .is_paid / .is_pay_subscribe

`raw=true`（原始，本接口默认）:

data 顶层字段与精简版一致（biz_username / is_end / count / next_offset / pages），但 articles[] 为完整原始群发条目（camelCase 嵌套）:

单条: $.data.articles[N].appMsg（含 baseInfo / detailInfo）、$.data.articles[N].baseInfo（msgId / msgType / dateTime / status）

图文正文在 $.data.articles[N].appMsg.detailInfo（一次群发可含多篇：头条 / 次条）

翻页同样用顶层 next_offset 回传 offset。做列表展示建议直接用 raw=false，路径更干净。

[English]

Purpose:

Pass a gh_username to get the account's historical article list. Two pagination modes:

Manual paging (recommended for incremental / precise control): max_pages = 1 (default) fetches a single page → take next_offset (base64 cursor) from the response → pass it as offset in the next request; is_end truthy means the last page.

Auto paging: max_pages > 1 — auto-continues, dedups across pages by article id, returns merged multi-page results; stops early at the last page.

Price: $0.01 per request

⏱️ Due to WeChat server latency, this endpoint responds slowly; please set your client request timeout to 30 seconds — a timeout that is too small may result in being billed without receiving the response.

Parameters:

username: Official account gh_username (gh_…). E.g. gh_363b924965e9

page_size: Optional, default 20, range 10-20. Articles per page.

max_pages: Optional, default 1, range 1-10. 1=single page (manual paging via offset); >1=auto-fetch and merge with dedup.

offset: Optional pagination cursor (base64), leave empty for the first page; for manual paging (max_pages=1) pass next_offset from the previous response. E.g. CAMQChiS5KfRBiAKOJLkp9EGQABIAVgAYABwAQ==

raw: Optional, default True. True=raw; False=simplified parsing.

Return:

Article list with pagination cursor

Tip: offset is a base64 cursor (contains +/=), hence POST body. With auto paging (max_pages>1), offset usually doesn't need to be passed manually.

Response structure & JSON Path:

`raw=false` (simplified, snake_case):

Account username: $.data.biz_username

Is last page (0/1): $.data.is_end

Articles returned this time: $.data.count

Next-page cursor (pass back as offset for manual paging; null at the last page): $.data.next_offset

Pages actually fetched: $.data.pages

Article list: $.data.articles[]

Single article (N is the index):

Article appmsgid: $.data.articles[N].app_msg_id

Title: $.data.articles[N].title

Digest: $.data.articles[N].digest

URL: $.data.articles[N].url

Cover: $.data.articles[N].cover (multi-ratio $.data.articles[N].covers)

Publish / update timestamps: $.data.articles[N].create_time / .update_time

Position / type within the batch: $.data.articles[N].idx / .msg_type / .item_show_type

Image count / paid flags: $.data.articles[N].pic_count / .is_paid / .is_pay_subscribe

`raw=true` (raw, default for this endpoint):

data top-level fields match the simplified version (biz_username / is_end / count / next_offset / pages), but articles[] are full raw batch entries (nested camelCase):

Per entry: $.data.articles[N].appMsg (with baseInfo / detailInfo), $.data.articles[N].baseInfo (msgId / msgType / dateTime / status)

Article bodies are in $.data.articles[N].appMsg.detailInfo (one batch may contain multiple articles: headline / secondary)

Pagination also uses top-level next_offset passed back as offset. For list display, prefer raw=false for cleaner paths.

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

curl --location 'https://api.tikhub.io/api/v1/wechat_mp/v2/fetch_account_articles' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "username": "gh_363b924965e9", "page_size": 20, "max_pages": 1, "offset": "string", "raw": true }'

{ "code": 200, "request_id": "string", "message": "Request successful. This request will incur a charge.", "message_zh": "请求成功，本次请求将被计费。", "support": "Discord: https://discord.gg/aMEAS8Xsvz", "time": "string", "time_stamp": 0, "time_zone": "America/Los_Angeles", "docs": "string", "cache_message": "string", "cache_message_zh": "string", "cache_url": "string", "router": "", "params": {}, "data": null }

获取公众号文章列表/Get WeChat MP Account Articles

[中文]

用途:

参数:

返回:

响应结构与 JSON Path:

`raw=false`（精简解析，snake_case）:

`raw=true`（原始，本接口默认）:

[English]

Purpose:

Parameters:

Return:

Response structure & JSON Path:

`raw=false` (simplified, snake_case):

`raw=true` (raw, default for this endpoint):

Request

Responses

获取公众号文章列表/Get WeChat MP Account Articles

[中文]#

用途:#

参数:#

返回:#

响应结构与 JSON Path:#

raw=false（精简解析，snake_case）:#

raw=true（原始，本接口默认）:#

[English]#

Purpose:#

Parameters:#

Return:#

Response structure & JSON Path:#

raw=false (simplified, snake_case):#

raw=true (raw, default for this endpoint):#

Request

Responses

[中文]

用途:

参数:

返回:

响应结构与 JSON Path:

`raw=false`（精简解析，snake_case）:

`raw=true`（原始，本接口默认）:

[English]

Purpose:

Parameters:

Return:

Response structure & JSON Path:

`raw=false` (simplified, snake_case):

`raw=true` (raw, default for this endpoint):