/autohome/series/spec

POST /api/autohome/series/spec

Price: 20 credits

Get Autohome Series Spec Table

How to use it

Get the parameter and equipment table of the trims Autohome currently lists for one car series, one row per trim with its guide price in CNY. In parameter values a filled dot marks standard equipment, a hollow dot an option and a dash absence. Series 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: "AutohomeSpec")
• id integer required
• name string nullable
• series_id integer nullable
• series_name string nullable
• brand_id integer nullable
• brand_name string nullable
• sale_state integer nullable
• year integer nullable
• price_text string nullable
• min_price number nullable
• dealer_price number nullable
• currency string nullable
• tags array (default: [])
• params array (default: [])
  • @type string (default: "AutohomeSpecParam")
  • item_id integer nullable
  • group string nullable
  • section string nullable
  • name string nullable
  • value string nullable
  • extra_price string nullable
  • video_url string nullable
  • options array (default: [])
    • @type string (default: "AutohomeSpecOption")
    • name string nullable
    • value string nullable
    • extra_price string nullable
  • color_type integer nullable
  • colors array (default: [])
    • @type string (default: "AutohomeSpecColor")
    • name string nullable
    • hex string nullable
    • extra_price number nullable
    • image_count integer nullable
    • url 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 or it has no spec table. 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.