/toutiao/articles

POST /api/toutiao/articles

Price: 5 credits

Get a Toutiao (toutiao.com) article by id or URL

How to use it

Get one Toutiao article by its numeric id or its toutiao.com article URL. Returns the article body, author and engagement counters. Use toutiao/articles/comments for the comment thread.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — Toutiao article id or article URL (examples: "7684660779384701455", "https://www.toutiao.com/article/7684660779384701455/"; minLength: 1)

Response

• @type string (default: "ToutiaoArticle")
• id string required
• item_id string nullable
• url string required
• article_type string nullable
• abstract string nullable
• text string nullable
• html string nullable
• source string nullable
• tag string nullable
• keywords array (default: [])
• image string nullable
• images array (default: [])
• video_id string nullable
• media_site_url string nullable
• group_source integer nullable
• is_original boolean nullable
• is_exclusive boolean nullable
• is_comment_disabled boolean nullable
• published_at integer nullable
• modified_at integer nullable
• like_count integer nullable
• comment_count integer nullable
• read_count integer nullable
• impression_count integer nullable
• share_count integer nullable
• favorite_count integer nullable
• forward_count integer nullable
• bury_count integer nullable
• video_watch_count integer nullable
• danmaku_count integer nullable
• author object nullable
  • @type string (default: "ToutiaoArticleAuthor")
  • id string nullable
  • numeric_id string nullable
  • name string nullable
  • image string nullable
  • description string nullable
  • is_verified boolean nullable
  • verification_info string nullable
  • follower_count integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Article not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.