POST /api/autohome/articles
Price: 10 credits
Get Autohome Article
Get the full body of one Autohome news article by its URL or yyyymm/id path, as plain text and as HTML, together with the car series the article mentions and their guide price ranges. URLs come from autohome/articles/news.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)article string required — Autohome news article URL, or its <yyyymm>/<id> path (examples: "https://www.autohome.com.cn/news/202607/1315940.html", "202607/1315940"; minLength: 1)@type string (default: "AutohomeArticle")id integer requiredurl string requiredsummary string nullabletext string nullablehtml string nullableimage string nullableimages array (default: [])article_type string nullablechannel string nullablecategory string nullablecategory_id integer nullableauthor_id integer nullableauthor_name string nullableauthor_image string nullablecoauthors array (default: [])@type string (default: "AutohomeArticleAuthor")id integer nullablename string nullablerole string nullableimage string nullableprovince string nullablepublished_at integer nullableview_count integer nullablecomment_count integer nullableis_comment_closed boolean nullabletags array (default: [])@type string (default: "AutohomeArticleTag")id integer nullablename string nullablekeywords array (default: [])series_ids array (default: [])mentioned_series array (default: [])@type string (default: "AutohomeArticleSeries")id integer nullablename string nullableimage string nullablemin_price number nullablemax_price number nullablerating number nullablelevel_name string nullablebrand_id integer nullablemanufacturer_id integer nullablerelated_videos array (default: [])@type string (default: "AutohomeArticleVideo")id integer nullableurl string nullableimage string nullableduration string nullableplay_count integer nullable422 — 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. Check the article URL. 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.