/auto8891/models/search

POST /api/auto8891/models/search

Price: 5 credits

Search the new-car model catalogue on 8891 (Taiwan), most viewed first: by brand, body type and fuel, on sale or discontinued. Each row carries the model's brand, new-car price range, trim count, current dealer discount and links to its specifications and used cars.

How to use it

Brand ids appear in brand_id here and in auto8891/listings/search rows.

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 models to return (min: 1; max: 1000)
• brand_id string nullable — Brand id, as returned in brand_id (examples: "46"; pattern: ^\d{1,9}$)
• body_type string nullable — Body type (one of: "suv", "sedan", "hatchback", "mpv", "wagon", "sports_car", "convertible", "pickup")
• fuel string nullable — Fuel or powertrain (one of: "gasoline", "diesel", "hybrid", "electric")
• discontinued boolean — Discontinued models instead of models on sale (default: false)

Response

• @type string (default: "Auto8891Model")
• id string required
• name string nullable
• brand string nullable
• brand_id string nullable
• price_min number nullable
• price_max number nullable
• price_text string nullable
• trim_count integer nullable
• highlight string nullable
• discount string nullable
• max_discount string nullable
• image string nullable
• url string nullable
• specs_url string nullable
• used_cars_url string nullable
• is_discontinued boolean nullable

Errors

• 422 — Unknown body type or fuel, 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.