/autohome/forum/threads

POST /api/autohome/forum/threads

Price: 10 credits

Get Autohome Series Forum Threads

How to use it

List threads of the Autohome club forum attached to one car series, most recently replied first, with author, publish and last-reply time, views, replies and summary. The source serves at most 10000 threads per forum. Pass a row url to autohome/forum/thread for the post body and replies.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• series_id integer required — Autohome series id whose forum to list, as in autohome.com.cn/<id>/ (examples: 692; min: 1)
• count integer required — Max number of threads to return (examples: 100; min: 1; max: 1000)

Response

• @type string (default: "AutohomeForumThread")
• id integer required
• url string nullable
• subtitle string nullable
• summary string nullable
• thread_type string nullable
• author_id integer nullable
• author_name string nullable
• forum_id integer nullable
• forum_name string nullable
• published_at integer nullable
• last_reply_at integer nullable
• view_count integer nullable
• reply_count integer nullable
• word_count integer nullable
• image_count integer nullable
• images array (default: [])
• tag_ids array (default: [])
• is_featured boolean nullable
• is_elite boolean nullable
• is_video boolean nullable
• is_solved boolean nullable
• is_comment_closed boolean nullable
• reward_coins integer nullable
• hot_score number nullable
• video_title string nullable
• video_cover string nullable
• video_duration integer nullable
• ip_province string nullable
• ip_city string nullable
• global_id string 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 — Forum not found. Check the series id. 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.