/iaai/vehicles/search

POST /api/iaai/vehicles/search

Price: 20 credits

Search IAAI salvage and insurance vehicles open for upcoming auctions by keyword, make, model, year, branch or auction date, with damage, odometer, title document, branch and Buy Now price for each.

How to use it

Find damaged or recovered vehicles headed to IAAI auctions, or list one branch's sale by passing branch_id with auction_date. Pass a result id to iaai/vehicles for the full condition and photos.

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 vehicles to return (min: 1; max: 1000)
• query string nullable — Free-text search as typed into the IAAI search box (examples: "honda civic")
• make string nullable — Vehicle make (examples: "FORD")
• model string nullable — Vehicle model (examples: "CIVIC")
• year_min integer nullable — Earliest model year (min: 1900; max: 2100)
• year_max integer nullable — Latest model year (min: 1900; max: 2100)
• branch_id string nullable — Branch id from iaai/branches/search (examples: "746"; pattern: ^\d{1,5}$)
• auction_date string nullable — Only vehicles in the auction held on this date (format: date; examples: "2026-09-21")

Response

• @type string (default: "IaaiVehicle")
• id string required
• tenant string required
• url string required
• stock_number string nullable
• vin_masked string nullable
• image string nullable
• title_sale_doc string nullable
• primary_damage string nullable
• secondary_damage string nullable
• loss_type string nullable
• inventory_added_text string nullable
• vehicle_type string nullable
• vehicle_subtype string nullable
• odometer integer nullable
• odometer_text string nullable
• start_code string nullable
• airbags string nullable
• key string nullable
• exterior_color string nullable
• interior_color string nullable
• engine string nullable
• fuel_type string nullable
• cylinders string nullable
• transmission string nullable
• drive_line_type string nullable
• body_style string nullable
• country_of_origin string nullable
• branch_name string nullable
• branch_id string nullable
• lane_run string nullable
• aisle_stall string nullable
• market string nullable
• seller string nullable
• seller_type string nullable
• actual_cash_value number nullable
• region string nullable
• auction_date string nullable
• auction_date_text string nullable
• buy_now_price number nullable

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.