/che168/dealers

POST /api/che168/dealers

Price: 5 credits

Get Che168 Dealer

How to use it

Get one Che168 used-car dealer by id: its storefront name and badges, cars on sale and sold, the buyer review count, and the reviewer name, star score and date of the buyer reviews shown on the storefront. total_score/star_score/service_score/shop_score/car_score are Che168's own dealer badge scores (4.0-4.5, shop_score almost always 4.0), not an average of this dealer's own reviews: they cluster at the same level whether review_count is 0 or in the thousands. Dealer ids come from che168/listings/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• dealer_id integer required — Che168 dealer id, as in dealer_id of a che168/listings/search row (examples: 225625; min: 1)

Response

• @type string (default: "Che168Dealer")
• id integer required
• url string required
• name string nullable
• badges array (default: [])
• on_sale_count integer nullable
• sold_count integer nullable
• ip_location string nullable
• review_count integer nullable
• total_score number nullable — Che168's own dealer badge score, 4.0-4.5 on the sampled dealers regardless of review_count (0 to 3167 reviews measured at the same level); not a review-derived average for this dealer.
• star_score number nullable — Che168's own dealer badge score, 4.0-4.5 on the sampled dealers regardless of review_count; not a review-derived average for this dealer.
• service_score number nullable — Che168's own dealer badge score, 4.0-4.5 on the sampled dealers regardless of review_count; not a review-derived average for this dealer.
• shop_score number nullable — Che168's own dealer badge score, 4.0 on all but two of 39 sampled dealers (the two at 5.0) regardless of review_count; not a review-derived average for this dealer.
• car_score number nullable — Che168's own dealer badge score, 4.0-4.5 on the sampled dealers regardless of review_count; not a review-derived average for this dealer.
• recent_reviews array (default: [])
  • @type string (default: "Che168DealerReview")
  • id integer required
  • user_name string nullable
  • user_image string nullable
  • score number nullable
  • posted_at 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 — Dealer not found. Check the dealer 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.