usernameRequiredbody · string
Official account username. Three forms are supported: `gh_…`, `gh_…@app` (mini-program-linked accounts) and custom WeChat IDs (e.g. `nikejdi`). Taken from `$.data.content.user_name` of the article detail endpoints
POST$0.013 per request · $13.00 per 1,000 requests
Fetch account articles
Get WeChat MP Account Articles
Endpoint
POST https://getvibeapi.com/v1/social/wechat_mp/v2/fetch_account_articlesExample
curl -sS "https://getvibeapi.com/v1/social/wechat_mp/v2/fetch_account_articles" \
-H "Authorization: Bearer $GETVIBE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary '{"username":"value"}'Send your key in the Authorization: Bearer header. You pay only for requests the data provider accepts. Requests it rejects (errors, timeouts, invalid parameters) are not billed. A valid request that returns an empty or not-found result from the platform is billed.
Parameters
page_sizebody · integer
next_offset/Articles per page (default 20). NOTE: WeChat currently ignores this parameter — the count is decided by the account itself; paginate with offset / next_offset
offsetbody · string
Pagination cursor (base64), leave empty for first page; for the next page pass next_offset from the previous response
item_show_typebody · integer
Content tab: empty/0=articles (default), 5=videos, 7=audios, 8=image-text posts
rawbody · boolean
True=raw response; False=simplified parsed structure
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| username | body | string | Yes | Official account username. Three forms are supported: `gh_…`, `gh_…@app` (mini-program-linked accounts) and custom WeChat IDs (e.g. `nikejdi`). Taken from `$.data.content.user_name` of the article detail endpoints |
| page_size | body | integer | No | next_offset/Articles per page (default 20). NOTE: WeChat currently ignores this parameter — the count is decided by the account itself; paginate with offset / next_offset |
| offset | body | string | No | Pagination cursor (base64), leave empty for first page; for the next page pass next_offset from the previous response |
| item_show_type | body | integer | No | Content tab: empty/0=articles (default), 5=videos, 7=audios, 8=image-text posts |
| raw | body | boolean | No | True=raw response; False=simplified parsed structure |