WeChat Official Accounts Today's account articles API

Temporarily unavailable

We are restoring this capability. Until then calls usually fail or return no results; failed calls and empty results are not charged.

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Track what one WeChat Official Account has published today, with each article's title, link, cover, publish time, position and original or deleted flags. It covers the current day only and is a pull you schedule, not a real-time subscription.

WeChat Official Account Today's account articles returns each article one account has put out on the current day, given account, with its headline, link and cover image, when it went out, its position, whether it claims originality or has been removed, and the account's name and IDs. It is built for daily monitoring: media watchers, PR teams and analysts call it on a schedule to pick up each account's new articles without re-reading its whole history.

Pass the same identifiers the other account capabilities take, such as the gh_ raw ID. Each article keeps its id and url, so a scheduled job can skip what it already stored, and account_ghid on every row keeps articles tied to the right account even when display names look alike. For earlier days, read the account with the WeChat Account articles capability.

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 Today's account articles endpoint (wechat_oa/account_today_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_today_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 of 1 or more. The default applies when you leave it out, and a call can return fewer rows.
- 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_today_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_today_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–)`	No	-	The most rows to return in this call, an integer of 1 or more. The default applies when you leave it out, and a call can return fewer rows.

Code samples

bash

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_today_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

Field preview

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.

json

{
  "id": "req_…",
  "platform": "wechat_oa",
  "action": "account_today_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 does an empty result mean?

It can simply mean that the account has not published anything yet on the current day. A call that returns no rows is not charged, so a monitoring job can simply check again later the same day instead of treating the empty answer as an error.

How is this different from Account articles?

Account articles reads an account's earlier articles, while this capability returns only the current day's. Both take the same account value and return the same fields, so a daily job can rely on this one and fall back to Account articles to fill in a day it missed.

Which time zone is `posted_at` in?

UTC, as an ISO 8601 timestamp. China Standard Time is eight hours ahead, so an article pushed shortly after midnight in Beijing carries the previous date in UTC; convert before you group articles by day. A non-standard time string from the platform is passed through unchanged, so parse defensively.

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).