WeChat Official Accounts Account articles API
May be temporarily unavailable at peak times
This capability may be temporarily unavailable at peak times; try again later. Failed calls are not charged.
API health
- 24h health
- Normal
- 24h average time
- —
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Pull the article history of one WeChat Official Account, 8 by default and up to 160 per call, with title, link, cover, publish time, position and original or deleted flags. Pass a WeChat ID, gh_ raw ID or account link, not a personal WeChat ID; one batch may not cover the full archive.
WeChat Official Account articles lists the articles one account has published, given account. Each row carries the title, link, cover image, publish time, position, whether it is marked original and whether it has been deleted. Use it to see what an account has been writing and how often it posts, for account evaluation, reviewing a competitor's content or building an industry article library.
account takes a WeChat ID, the raw ID starting with gh_, or an account or article link that identifies the account; a personal WeChat ID does not work. position is the article's slot in its push, the lowest being the lead article; is_deleted marks removed articles and is_original those that claim original authorship. account_ghid is the account's unique ID within WeChat, which makes it the right key for de-duplication.
Price $5.56 per 1,000 requests ($0.005556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.
Please help me write a data collection script with the EveryInfra WeChat Official Accounts Account articles endpoint (wechat_oa/account_articles).
Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to wechat_oa and action to account_articles, and put the parameters inside params.
- Required parameters:
- account: Identifies the target WeChat Official Account using its WeChat ID, raw ID (starting with gh_), or a resolvable account/article URL. It does not accept personal WeChat IDs.
- Optional parameters:
- limit: The most rows to return in this call, an integer from 1 to 160. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 8)
- Returns a list of records. Main fields of each record: id, title, url, cover_image_url (Cover image URL of the article), posted_at, position (Slot of the article within one push: th…), is_original (Whether the article carries an original…), is_deleted (Whether the content has been deleted), account_name (Name of the Official Account that publi…), account_id (Official Account ID (its WeChat ID)), account_ghid (The account's raw ID starting with gh_,…).
- Example request body:
{
"platform": "wechat_oa",
"action": "account_articles",
"params": {
"account": "36氪"
}
}
- Price: $5.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | wechat_oa | Platform identifier, fixed value. |
action | body | string | Yes | account_articles | Capability identifier, fixed value. |
account | body.params | Not declared | Yes | - | Identifies the target WeChat Official Account using its WeChat ID, raw ID (starting with gh_), or a resolvable account/article URL. It does not accept personal WeChat IDs. Used by account_principal (for publisher profile metadata), account_articles (for historical post lists), and account_today_articles (for posts published today). |
limit | body.params | integer (1–160) | No | 8 | The most rows to return in this call, an integer from 1 to 160. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |
Code samples
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "wechat_oa",
"action": "account_articles",
"params": {
"account": "36氪"
}
}'[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.
{
"id": "req_…",
"platform": "wechat_oa",
"action": "account_articles",
"results": [
{
"id": …,
"title": …,
"url": …,
"cover_image_url": …,
"posted_at": …,
"position": …,
"is_original": …,
"is_deleted": …,
"account_name": …,
"account_id": …,
"account_ghid": …,
"platform": …
}
],
"count": …,
"billing": {
"charged": …,
"charged_usd": …,
"balance_after_usd": …,
…
},
"quota": { … }
}Response fields
Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
title | Title. null when the platform has no titles (for example text-only posts). |
url | Link to the record on the platform. |
cover_image_url | Cover image URL of the article. |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
position | Slot of the article within one push: the lowest number is the lead article. It is not a ranking by reads or popularity. |
is_original | Whether the article carries an original-content declaration. |
is_deleted | Whether the content has been deleted. |
account_name | Name of the Official Account that published the article. |
account_id | Official Account ID (its WeChat ID). |
account_ghid | The account's raw ID starting with gh_, unique within WeChat. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
FAQ
What can I pass as account?
A WeChat ID, the raw ID that starts with gh_, or an account or article link that identifies the account. Personal WeChat IDs do not work. If you only know the account's name, find its ID first with the WeChat Account search capability.
How do I spot original or deleted articles?
is_original is true when the article claims original authorship. is_deleted is true when the content has been removed; such links may no longer open, so count those articles separately.
How should I de-duplicate accounts?
Use account_ghid, the raw ID starting with gh_, which is unique within WeChat. Account names can change over time, so they make poor keys for the articles you store.
Errors and billing
- 401
- Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
- 422
- Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
- 402
- Insufficient balance. Top up first.
- 429
- The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
- 503
- Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
- 200 empty
- The request completed without data and is not charged (billing.reason = empty_result_refunded).