/autohome/series/reviews

POST /api/autohome/series/reviews

Price: 5 credits

Get Autohome Series Owner Reviews

How to use it

Get owner reviews (koubei) of one Autohome car series, newest first: the trim bought, purchase price, place and date, mileage, per-aspect scores and the written sections. The source serves at most 2000 reviews per series. Pass a row id to autohome/reviews for the full review page.

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, as in autohome.com.cn/<id>/ (examples: 692; min: 1)
• count integer required — Max number of owner reviews to return (examples: 20; min: 1; max: 1000)
• model_year_id integer nullable — Autohome model year id to keep only reviews of that model year, as model_year_id on a row (examples: 21138; min: 1)

Response

• @type string (default: "AutohomeSeriesReview")
• id string required
• review_id integer nullable
• url string required
• user_id integer nullable
• user_name string nullable
• user_image string nullable
• user_owner_level integer nullable
• user_influencer_level integer nullable
• is_verified_owner boolean nullable
• posted_at integer nullable
• review_type integer nullable
• series_name string nullable
• spec_id integer nullable
• spec_name string nullable
• model_year integer nullable
• model_year_id integer nullable
• mileage string nullable
• purchase_price number nullable
• purchase_price_text string nullable
• currency string nullable
• purchase_place string nullable
• purchase_date string nullable
• ownership_period string nullable
• dealer_id integer nullable
• dealer_name string nullable
• fuel_consumption number nullable
• battery_consumption number nullable
• average_score number nullable
• scores array (default: [])
  • @type string (default: "AutohomeNameValue")
  • name string nullable
  • value string nullable
• sections array (default: [])
  • @type string (default: "AutohomeReviewSection")
  • section_id integer nullable
  • text string nullable
• extra_info array (default: [])
  • @type string (default: "AutohomeNameValue")
  • name string nullable
  • value string nullable
• purposes array (default: [])
• medals array (default: [])
  • @type string (default: "AutohomeReviewMedal")
  • medal_type integer nullable
  • name string nullable
• images array (default: [])
• photo_count integer nullable
• media_count integer nullable
• view_count integer nullable
• comment_count integer nullable
• helpful_count integer nullable
• is_recommended boolean nullable
• spring_range integer nullable
• summer_range integer nullable
• winter_range integer nullable
• routine_range 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 — Series 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.