/guazi/auctions/search

POST /api/guazi/auctions/search

Price: 5 credits

Search Guazi Auction Lots

How to use it

Search Guazi's used-car auction lots by keyword, make id, USD price range and body type (SUV = 3); no sort is supported (the source drops auction lots from the results once a sort is sent). Rows carry the current price, the auction name and type, and the seconds left on the countdown at fetch time.

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 auction lots to return (examples: 30; min: 1; max: 1000)
• keyword string nullable — Free-text search such as a make or model name (examples: "toyota")
• brand_id integer nullable — Guazi make id, as returned in brand_id of a result row (examples: 1195; min: 1)
• min_price integer nullable — Lowest price in USD (examples: 0; min: 0)
• max_price integer nullable — Highest price in USD (examples: 7000; min: 1)
• body_type array nullable — Guazi body-type codes, sent as autoTypes. Only 3 (SUV) carries a published label; 1, 4, 5, 6, 7, 8 are accepted by the source and each returns a distinct total but their labels are not published (examples: [3])
• sort null — Not supported on auction lots: the source drops the auction listings once a sort is sent

Response

• @type string (default: "GuaziProduct")
• id string required
• url string nullable
• image string nullable
• brand_name string nullable
• brand_id integer nullable
• series_id integer nullable
• car_id integer nullable
• manufacture_date string nullable
• registration_date string nullable
• mileage_km integer nullable
• fuel_type string nullable
• fuel_type_code integer nullable
• engine string nullable
• transmission string nullable
• battery_capacity string nullable
• ev_range string nullable
• total_range string nullable
• is_electrified boolean nullable
• price number nullable
• list_price number nullable
• discount_amount number nullable
• currency string nullable
• is_price_shown boolean nullable
• exchange_rate number nullable
• product_status integer nullable
• business_type integer nullable
• auction_name string nullable
• auction_type integer nullable
• auction_type_text string nullable
• auction_sequence integer nullable
• auction_mark string nullable
• preview_end_at integer nullable
• countdown_seconds integer nullable
• display_sale integer nullable
• is_guazi_owned boolean nullable
• has_video boolean nullable
• labels array (default: [])
  • @type string (default: "GuaziLabel")
  • label_type integer nullable
  • name string nullable
  • description string nullable
• label_ids array (default: [])

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 — 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.