/auto8891/listings/search

POST /api/auto8891/listings/search

Price: 5 credits

Search used cars for sale on 8891 in Taiwan: by keyword, brand and model, price, region, transmission, fuel, certified dealer or one dealer's stock. Each row carries price, year, mileage, engine, colour, region, photos, views, the seller's promotion and dealer badges.

How to use it

Get a car's full specification, equipment, seller and description with auto8891/listings. Find dealer ids with auto8891/dealers/search.

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 listings to return (min: 1; max: 12000)
• keyword string nullable — Words to find in listings (examples: "Camry"; minLength: 1)
• brand string nullable — Brand name (examples: "toyota", "mercedes-benz"; minLength: 1)
• model string nullable — Model name within the brand (examples: "camry"; minLength: 1)
• price_min number nullable — Minimum price, TWD (examples: 300000; min: 0)
• price_max number nullable — Maximum price, TWD (examples: 600000; min: 0)
• region string nullable — City or county where the car is (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")
• transmission string nullable — Transmission type (one of: "manual", "automatic", "automated_manual", "manumatic", "cvt")
• fuel string nullable — Fuel or powertrain (one of: "gasoline", "diesel", "hybrid", "electric")
• certification string nullable — Only cars from dealers with this certification (one of: "save", "carok")
• dealer_id string nullable — Only cars of this dealer (examples: "173"; pattern: ^\d{1,9}$)
• sort string — Result order (default: "relevance"; one of: "relevance", "price_asc", "price_desc", "year_desc", "mileage_asc")

Response

• @type string (default: "Auto8891Listing")
• id string required
• url string required
• subtitle string nullable
• brand string nullable
• brand_id string nullable
• model string nullable
• model_id string nullable
• trim string nullable
• trim_id string nullable
• manufacture_year integer nullable
• model_year integer nullable
• price number nullable
• price_text string nullable
• mileage_km number nullable
• engine string nullable
• transmission string nullable
• color string nullable
• region string nullable
• seller_member_id string nullable
• image string nullable
• large_image string nullable
• dashboard_image string nullable
• video_url string nullable
• promotion string nullable
• promotion_type string nullable
• badges array (default: [])
• day_view_count integer nullable
• view_count integer nullable
• dealer_review_count integer nullable
• is_audited boolean nullable
• has_inspection_report boolean nullable
• is_physical_shop boolean nullable
• is_top_dealer boolean nullable
• is_promoted boolean nullable
• is_auction boolean nullable
• posted_at integer nullable
• renewed_at integer nullable

Errors

• 422 — model without brand, an inverted price range, or an unknown region, transmission, fuel or sort 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.