Skip to main content
POST
Get WeChat MP Account Articles
Get WeChat MP Account Articles Pricing — billed per successful call; the final charge scales by your plan multiplier. Charged only when the upstream response body code is 200.
Response structure is not yet fully documented — refer to the actual API response.

Example

Authorizations

Authorization
string
header
required

AIsa API key. Get yours at https://aisa.one

Body

application/json
username
string
required

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

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

Maximum string length: 80
Pattern: ^[0-9A-Za-z][-_0-9A-Za-z]{1,63}(@[0-9A-Za-z]{1,16})?$
Example:

"gh_363b924965e9"

page_size
integer
default:20

Articles per page (default 20). WeChat currently ignores this parameter; the account determines the returned count. Paginate using offset and next_offset.

Required range: 1 <= x <= 100
offset
string | null
default:""

Optional pagination cursor (base64), leave empty for the first page; for the next page pass next_offset from the previous response. E.g. CAMQChiS5KfRBiAKOJLkp9EGQABIAVgAYABwAQ==

Maximum string length: 8192
Pattern: ^[A-Za-z0-9+/=_-]*$
item_show_type
integer | null

Optional content tab (matches the "Articles / Videos / Audios" tabs on the account homepage). Empty / 0=articles (default), 5=videos, 7=audios, 8=image-text posts. Omitting it = articles, behavior unchanged.

raw
boolean
default:true

True=raw response; False=simplified parsed structure

Response

200 - application/json

Successful response. The outer object follows ResponseModel; the endpoint-specific payload is in data.

Return

  • Single page of articles with pagination cursor

Tip: offset is a base64 cursor (contains +/=), hence POST body. This endpoint fetches a single page only and does not auto-paginate.

Response structure & JSON Path

raw=false (simplified, snake_case):

  • Account username: $.data.biz_username
  • Is last page (0/1): $.data.is_end
  • Articles returned on this page: $.data.count
  • Next-page cursor (pass back as offset; null at the last page): $.data.next_offset
  • 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), 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.
code
integer
default:200

HTTP status code

request_id
string | null

Unique request identifier

message
string
default:Request successful. This request will incur a charge.

Response message (EN-US)

message_zh
string
default:请求成功,本次请求将被计费。

Response message (ZH-CN)

support
string
default:Discord: https://discord.gg/aMEAS8Xsvz

Support message

time
string

The time the response was generated

time_stamp
integer

The timestamp the response was generated

time_zone
string
default:America/Los_Angeles

The timezone of the response time

docs
string | null

Link to the API Swagger documentation for this endpoint

cache_message
string | null
default:This response is cached and accessible via the URL below for 24 hours at no extra cost. The cache is for request tracing only — it doesn't affect the API's data freshness and won't be returned through the API again.

Cache message (EN-US)

cache_message_zh
string | null
default:本次响应已缓存,可通过下方 URL 直接查看,有效期 24 小时,访问缓存链接无额外费用。缓存仅用于请求溯源,不影响接口数据的时效性,也不会再次通过接口返回。

Cache message (ZH-CN)

cache_url
string | null

The URL to access the cached result

router
string
default:""

The endpoint that generated this response

params
any
default:{}

The parameters used in the request

data
any | null

Endpoint-specific response payload. The official shared model does not declare a fixed type or field set. Use the operation's documented return fields or response example; an operation-specific schema, when present, describes the documented fields. Undocumented fields must be read from the actual response rather than assumed.