/che168/listings

POST /api/che168/listings

Price: 10 credits

Get Che168 Used Car Listing

How to use it

Get one Che168 used-car listing by page URL, or by listing id plus dealer id from che168/listings/search: asking price in CNY, the vehicle profile the page lists with inspection and insurance dates, the dealer card and the gallery.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• url string nullable — Che168 listing page URL (examples: "https://www.che168.com/dealer/225625/59718876.html")
• listing_id integer nullable — Listing id, as in id of a che168/listings/search row (examples: 59718876; min: 1)
• dealer_id integer nullable — Dealer id of the listing, as in dealer_id of a search row (examples: 225625; min: 1)

Response

• @type string (default: "Che168Listing")
• id integer required
• url string required
• price number nullable
• currency string nullable
• mileage_km integer nullable
• registration_date string nullable
• published_at integer nullable
• city_name string nullable
• emission_standard string nullable
• tags array (default: [])
  • @type string (default: "Che168ListingTag")
  • name string nullable
  • description string nullable
• attributes array (default: [])
  • @type string (default: "Che168ListingAttribute")
  • name string required
  • value string required
• dealer_id integer nullable
• dealer_name string nullable
• dealer_label string nullable
• dealer_address string nullable
• images array (default: [])

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 — Listing not found or no longer on sale. Check the URL or ids. 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.