/auto8891/dealers

POST /api/auto8891/dealers

Price: 5 credits

Get one used-car dealer on 8891: name, address, location, phone, LINE, contact person, business hours, brands, dealer unions, the dealer's introduction, years in business, cars on sale and in stock, deals closed, ratings for price, condition, satisfaction and recommendation, review count with tag counts, and the latest buyer reviews

How to use it

Find ids with auto8891/dealers/search; the dealer's cars are auto8891/listings/search by dealer_id.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Dealer id or URL (examples: "173", "https://www.8891.com.tw/findBuz-info-173.html")

Response

• @type string (default: "Auto8891DealerDetail")
• id string required
• url string nullable
• name string nullable
• member_id string nullable
• region string nullable
• address string nullable
• latitude number nullable
• longitude number nullable
• mobile string nullable
• contact_name string nullable
• line_url string nullable
• business_hours string nullable
• business_status string nullable
• business_types array (default: [])
• brands array (default: [])
• unions array (default: [])
• image string nullable
• description string nullable
• operating_years integer nullable
• on_sale_count integer nullable
• in_stock_count integer nullable
• in_stock_rate string nullable
• deal_count integer nullable
• ratings object nullable
  • @type string (default: "Auto8891DealerRatings")
  • overall number nullable
  • price number nullable
  • vehicle_condition number nullable
  • satisfaction number nullable
  • recommendation number nullable
• review_count integer nullable
• review_tags array (default: [])
  • @type string (default: "Auto8891ReviewTag")
  • key string nullable
  • label string required
  • count integer nullable
• latest_reviews array (default: [])
  • @type string (default: "Auto8891DealerReview")
  • id string required
  • author_name string nullable
  • author_image string nullable
  • text string nullable
  • score number nullable
  • in_store_score number nullable
  • price_score number nullable
  • information_score number nullable
  • service_score number nullable
  • car_brand string nullable
  • car_model string nullable
  • images array (default: [])
  • video_url string nullable
  • like_count integer nullable
  • is_transfer_verified boolean nullable
• is_top_dealer boolean nullable
• is_physical_shop boolean nullable
• is_verified boolean nullable

Errors

• 422 — id is not an 8891 dealer id or URL 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 — No dealer under that 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.