/dongchedi/series/models

POST /api/dongchedi/series/models

Price: 20 credits

Get every model trim of a Dongchedi car series with its full specification table

How to use it

Get the model trims of one Chinese car series from Dongchedi with official and dealer prices in CNY and the full specification table per trim: dimensions, powertrain, battery, chassis and equipment, each marked standard, optional or absent. Filter by sale status to get current, discontinued or upcoming trims.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• series string required — Dongchedi car series id or series page URL (examples: "20154", "https://www.dongchedi.com/auto/series/20154")
• count integer required — Max number of model trims to return (examples: 10; min: 1; max: 300)
• sale_status string — Only trims with this sale status; all returns every trim (default: "all"; one of: "all", "on_sale", "discontinued", "upcoming")

Response

• @type string (default: "DongchediModel")
• id string required
• name string nullable
• year integer nullable
• series_id string nullable
• series_name string nullable
• brand_id string nullable
• brand_name string nullable
• vehicle_type string nullable
• sale_status string nullable
• currency string (default: "CNY")
• official_price number nullable
• dealer_price number nullable
• specs array (default: [])
  • @type string (default: "DongchediSpec")
  • section string nullable
  • name string required
  • option string nullable
  • value string nullable
  • availability string nullable
  • option_price number 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.