/autohome/series

POST /api/autohome/series

Price: 5 credits

Get Autohome Car Series

How to use it

Get one Autohome car series by id: guide price range in CNY, brand, manufacturer, vehicle class, model years, owner rating with per-aspect scores and keywords, rival series scores, colours per trim and featured forum topics. Ids come from autohome/series/search.

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)

Response

• @type string (default: "AutohomeSeries")
• id integer required
• name string nullable
• url string required
• image string nullable
• transparent_image string nullable
• min_price number nullable
• max_price number nullable
• currency string nullable
• sale_state integer nullable
• brand_id integer nullable
• brand_name string nullable
• brand_logo string nullable
• manufacturer_id integer nullable
• manufacturer_name string nullable
• level_id integer nullable
• level_name string nullable
• energy_type integer nullable
• fuel_type_code integer nullable
• hot_spec_id integer nullable
• hot_spec_name string nullable
• new_energy_series_id integer nullable
• has_spec_table boolean nullable
• overseas_price string nullable
• overseas_price_country string nullable
• model_years array (default: [])
  • @type string (default: "AutohomeModelYear")
  • name string nullable
  • year integer nullable
  • sale_state integer nullable
• rating number nullable
• rating_scores array (default: [])
  • @type string (default: "AutohomeRatingScore")
  • name string nullable
  • type_key integer nullable
  • score number nullable
  • rank integer nullable
• review_keywords array (default: [])
  • @type string (default: "AutohomeReviewKeyword")
  • id integer nullable
  • text string nullable
  • mention_count integer nullable
  • sentiment integer nullable
  • is_electric_related boolean nullable
• competitors array (default: [])
  • @type string (default: "AutohomeCompetitor")
  • series_id integer nullable
  • name string nullable
  • score number nullable
  • best_aspect string nullable
  • best_aspect_score number nullable
  • new_car_pph integer nullable
  • new_car_pph_user_count integer nullable
  • reliability_pph integer nullable
  • reliability_pph_user_count integer nullable
• spec_colors array (default: [])
  • @type string (default: "AutohomeSpecColors")
  • spec_id integer nullable
  • spec_name string nullable
  • colors array (default: [])
    • @type string (default: "AutohomeColor")
    • id integer nullable
    • name string nullable
    • base_color_name string nullable
    • hex string nullable
• forum_topics array (default: [])
  • @type string (default: "AutohomeForumTopicLink")
  • id integer nullable
  • url string nullable
  • image 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 — 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.