Toutiao Article details API

POST

API health

24h health
Normal
24h average time
—
  • Healthy / normal
  • Available
  • Limited
  • Mostly down
Normal

Read a Toutiao article or video from its URL, with title, body text, cover, read or play count, likes, comments, shares and author verification. Full text or a transcript appears only when the page exposes it.

Price $0.56 per 1,000 requests ($0.000556 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 Toutiao Article details endpoint (toutiao/article).

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 toutiao and action to article, and put the parameters inside params.
- Required parameters:
  - url: Full URL to a specific article or video for the article action. In user-scoped actions where both url and user_id are supplied, url takes precedence to identify the profile page.
- Returns one object. Main fields: id, url, type, title, text, content_text, cover, read_count, play_count, like_count, comment_count, share_count; 22 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=toutiao.
- Example request body:
{
  "platform": "toutiao",
  "action": "article",
  "params": {
    "url": "https://www.toutiao.com/article/<ARTICLE_ID>/"
  }
}
- Price: $0.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

NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYestoutiaoPlatform identifier, fixed value.
actionbodystringYesarticleCapability identifier, fixed value.
urlbody.paramsNot declaredYes-Full URL to a specific article or video for the article action. In user-scoped actions where both url and user_id are supplied, url takes precedence to identify the profile page.

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": "toutiao",
  "action": "article",
  "params": {
    "url": "https://www.toutiao.com/article/<ARTICLE_ID>/"
  }
}'

[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": "toutiao",
  "action": "article",
  "results": {
    "id": …,
    "url": …,
    "type": …,
    "title": …,
    "text": …,
    "content_text": …,
    "cover": …,
    "read_count": …,
    "play_count": …,
    "like_count": …,
    "comment_count": …,
    "share_count": …,
    "source": …,
    "author_name": …,
    "author_id": …,
    "author_verified": …,
    "author_auth_info": …,
    "region": …,
    "posted_at": …,
    "platform": …,
    "duration_sec": …,
    "duration_seconds": …,
    "image_urls": …
  },
  "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.

FieldMeaning
idThe record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
urlLink to the record on the platform.
typeRecord type; values depend on the capability (for example video / image / text).
titleTitle. null when the platform has no titles (for example text-only posts).
textBody text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so).
content_textKeeps the platform's own meaning
coverKeeps the platform's own meaning
read_countKeeps the platform's own meaning
play_countKeeps the platform's own meaning
like_countLikes. null means the platform or this capability does not disclose it; it is not 0.
comment_countComments. null means not disclosed, not 0.
share_countShares. null means not disclosed, not 0.
sourceKeeps the platform's own meaning
author_nameAuthor's display name.
author_idAuthor's unique ID on the platform.
author_verifiedKeeps the platform's own meaning
author_auth_infoKeeps the platform's own meaning
regionKeeps the platform's own meaning
posted_atPublish 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.
platformSource platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).
duration_secKeeps the platform's own meaning
duration_secondsDuration in seconds. null for content that is not video or audio.
image_urlsArray of image links in the platform's display order; absent when there are no images.

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