/auto8891/dealers/search

POST /api/auto8891/dealers/search

Price: 5 credits

Search used-car dealers on 8891 in Taiwan by name, region or brand sold. Each row carries the dealer's address, location, phone, rating and review count, cars on sale and in stock, years in business, brands, featured cars and badges.

How to use it

Get a dealer's profile and review summary with auto8891/dealers, and its cars with 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)
• count integer required — Max number of dealers to return (min: 1; max: 2000)
• keyword string nullable — Dealer name words (examples: "福利"; minLength: 1)
• region string nullable — City or county (one of: "taipei", "keelung", "new_taipei", "hsinchu_city", "hsinchu_county", "taoyuan", "miaoli", "taichung", "changhua", "nantou", "chiayi_city", "chiayi_county", "yunlin", "tainan", "kaohsiung", "pingtung", "yilan", "taitung", "hualien", "penghu", "kinmen", "lienchiang")
• brand_id string nullable — Only dealers selling this brand, as returned in brand_id (examples: "46"; pattern: ^\d{1,9}$)

Response

• @type string (default: "Auto8891Dealer")
• id string required
• url string nullable
• name string nullable
• region string nullable
• address string nullable
• latitude number nullable
• longitude number nullable
• mobile string nullable
• image string nullable
• rating number nullable
• review_count integer nullable
• on_sale_count integer nullable
• in_stock_count integer nullable
• in_stock_rate string nullable
• operating_years integer nullable
• brands array (default: [])
  • @type string (default: "Auto8891DealerBrand")
  • id string nullable
  • name string required
• featured_cars array (default: [])
  • @type string (default: "Auto8891FeaturedCar")
  • id string required
  • brand string nullable
  • price number nullable
  • url string nullable
  • image string nullable
• news_title string nullable
• news_url string nullable
• is_top_dealer boolean nullable
• is_physical_shop boolean nullable
• is_promoted boolean nullable

Errors

• 422 — Unknown region or a non-numeric brand_id 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 — The entity was not found, or a precondition failed 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.