IAAI Scraper [Only $1💰] | Salvage Cars | VIN | Auction Data

IAAI Scraper

Scrape IAAI (IAA / Insurance Auto Auctions) salvage and used-vehicle auction lots across the US and Canada for dealer, rebuilder and market research: VIN, year, make, model and trim, damage and loss type, title brand and sale document, odometer, ACV and estimated repair cost, current bid, minimum bid and buy-now price, auction date, branch location and the full lot photo gallery.

The actor reads IAAI's server-rendered listing and lot pages over plain HTTP, so each lot is one cheap request, and it reads the embedded ProductDetailsVM JSON on a lot page for the full specification set.

Main Use Cases

• Dealer and rebuilder inventory sourcing from salvage auctions
• Salvage vehicle market research and price benchmarking (ACV, bids, buy-now)
• Building a structured vehicle and VIN database across US and Canada auctions
• Damage, title-brand and loss-type analysis for risk and pricing models
• Auction monitoring for specific makes, models, keywords or VIN fragments
• Parts and rebuild-cost estimation from damage and repair-cost fields

How It Works

IAAI listing pages render each lot as a server-side card, and a lot detail page carries an embedded ProductDetailsVM JSON block with the full vehicle data. The actor walks the listing pages and, when lot details are enabled, reads that JSON per lot:

Data	Source
Listing rows (one card per lot)	Server-rendered listing and search pages, 100 lots per page.
Listing pagination	IAAI's own POST /Search endpoint.
Full lot details	The lot page's embedded ProductDetailsVM JSON (odometer, ACV, buy-now, photos, branch coordinates, specs).
Photos	The public IAAI image resizer (vis.iaai.com) gallery URLs.

IAAI runs bot protection (Imperva / Incapsula). The actor leans on the server-rendered markup and the public JSON surfaces rather than challenge pages, and concurrency can be lowered if challenges appear.

Scrape IAAI Auction Lots And VINs Without An Official API

IAAI does not publish a self-serve public API for auction data. The internal Vehiclelisting API the site uses is not documented for third parties, and the practical alternatives are commercial providers that normalize Copart and IAAI data. This actor reads the same public pages a visitor sees:

• Start from listing, search or single-lot URLs in startUrls, or let the actor build a search URL from keyword, category or make when startUrls is empty.
• Walk up to maxPages result pages per start URL (100 lots per page) using IAAI's own search endpoint.
• Enrich each lot with its detail page (scrapeDetails) for odometer, ACV, repair cost, bids, buy-now, branch coordinates and specs.
• Keep or drop the photo gallery with includePhotos.

Note on cross-auction use: IAAI and Copart describe the same conditions differently (for example title brands and damage wording), so fields such as primaryDamage, lossType and titleBrand reflect IAAI's own vocabulary and should be normalized before you combine them with another auction's data.

Input Parameters

Field	Type	Required	Default	Notes
startUrls	array	No	Toyota cars listing	IAAI listing, search or lot URLs. Category listings, search pages and single lot pages are all supported.
keyword	string	No	empty	Free-text search (make, model, VIN fragment). Used only when startUrls is empty. Builds a search URL.
category	string	No	Cars	Vehicle category used to build the listing URL when startUrls is empty and no keyword is given.
make	string	No	empty	Vehicle make (for example Toyota) used to build a category listing URL when startUrls is empty and no keyword is given.
maxItems	integer	No	50	Maximum lots to save. Free users are capped at 10.
maxPages	integer	No	1	Maximum result pages walked per start URL (100 lots per page). Pagination uses IAAI's own search endpoint.
maxConcurrency	integer	No	8	Parallel pages. Higher is faster, but IAAI runs bot protection; drop to 2 to 3 if you see challenge pages instead of lot data.
scrapeDetails	boolean	No	true	Fetch each lot detail page and read its ProductDetailsVM JSON for full data. Each successfully parsed detail lot bills one lot-detail event; failed detail fetches are not billed.
includePhotos	boolean	No	true	Include the full photo gallery URLs on each lot.
proxy	object	No	Apify Proxy off	Proxy configuration used for the requests.

Output Fields

One item per lot in the default dataset:

• Identity: itemId, salvageId, stockNumber, url, title, year, make, model, trim.
• VIN: vin, vinMasked, vinStatus.
• Body and specs: bodyStyle, exteriorColor, interiorColor, engine, cylinders, fuelType, transmission, driveLineType, displacement, countryOfOrigin, vehicleType, vehicleSubType, vehicleClass, segment.
• Damage and title: primaryDamage, primaryDamageCode, secondaryDamage, secondaryDamageCode, lossType, lossTypeCode, titleType, titleCode, titleState, titleStateName, titleBrand, saleDocument.
• Condition: odometer, odometerUnit, odometerBrand, keysAvailable, keyFob, airbagState, startsDesc, startsCode, runAndDrive, operable, inventoryStatus, vehicleGrade, whoCanBuy.
• Auction: auctionDateTime, auctionDate, lane, slot, aisle, stall, currency, currentBid, minimumBidAmount, bidIncrement, buyNowPrice, buyNowAvailable, acv, estimatedRepairCost, saleHistory, seller.
• Location: branchName, market, region, providerGroup, location.
• Media: photoUrls, photoCount, thumbnail, image360Url, engineVideoExists, link360.
• Meta: scrapedAt, source.

Dataset view: overview.

Example Input And Output

Example input:

{
  "startUrls": [{ "url": "https://www.iaai.com/Vehiclelisting/Cars/Toyota" }],
  "maxItems": 50,
  "maxPages": 2,
  "scrapeDetails": true,
  "includePhotos": true
}

Example output row:

{
  "itemId": "46837687",
  "salvageId": "46837687",
  "stockNumber": "46837687",
  "url": "https://www.iaai.com/VehicleDetail/46837687~US",
  "title": "2021 Toyota Camry SE",
  "year": 2021,
  "make": "Toyota",
  "model": "Camry",
  "trim": "SE",
  "vin": "4T1G11AK0MU000000",
  "vinMasked": false,
  "bodyStyle": "Sedan",
  "fuelType": "Gasoline",
  "transmission": "Automatic",
  "driveLineType": "Front Wheel Drive",
  "primaryDamage": "Front End",
  "lossType": "Collision",
  "titleType": "Salvage",
  "titleBrand": "Salvage",
  "odometer": 41235,
  "odometerUnit": "mi",
  "runAndDrive": true,
  "keysAvailable": true,
  "currentBid": 5200.0,
  "buyNowPrice": 7900.0,
  "buyNowAvailable": true,
  "acv": 21500.0,
  "estimatedRepairCost": 8600.0,
  "auctionDateTime": "2026-10-20T15:30:00",
  "branchName": "Dallas",
  "region": "Southwest",
  "photoUrls": ["https://vis.iaai.com/resizer?imageKeys=46837687~SID~B1~S0~I1&width=640"],
  "photoCount": 14,
  "scrapedAt": "2026-10-13T09:00:00.000Z",
  "source": "iaai"
}

Integrations & Automation

Export results as JSON, CSV or Excel, read them through the Apify API, or push rows to a database, spreadsheet or BI tool with webhooks, Zapier or Make. For auction monitoring, schedule the actor daily (or a few times a day for fast-moving sales) with the same startUrls or keyword, so each run captures new lots and their current bids. Recurring runs also help the actor surface better in the Apify Store.

Related Actors

• easyapi/iaai-vehicle-detail-scraper
• shahidirfan/IAAI-Vehicles-Scraper
• scrapestorm/iaai-vehicles-scraper---cheap
• benthepythondev/iaai-vehicle-scraper
• memo23/copart-scraper

FAQ

Is there an official IAAI API?

No self-serve public one. IAAI (IAA) uses an internal vehicle-listing API for its own site, but it is not published for third parties. Teams that want IAAI data in bulk normally either scrape the public pages or buy normalized feeds from a commercial provider that combines Copart and IAAI. This actor reads the public pages and returns the lot-level fields directly.

What are the alternatives to this actor for IAAI data?

Alternatives include other Apify Store actors focused on IAAI lot details, and cross-auction data providers such as auctionsapi-style or apibara-style services that normalize Copart and IAAI. This actor returns IAAI lot rows (with optional enriched details and photos) priced per item.

How is IAAI data different from Copart data?

Both sell similar insurance-salvage inventory, but they label the same conditions differently. IAAI uses a stock number and an item ID per listing, Copart uses a lot number, and the same condition or title can be worded differently on each site. The same VIN can also appear on both auctions over its life. Normalize primaryDamage, lossType and titleBrand before combining the two.

Why am I getting fewer lots than maxItems?

Two reasons. Non-paying users are capped at 10 lots per run. Also, the number of lots also depends on how many result pages the run walks (maxPages) and how many startUrls you give it.

Do I need a proxy?

Not by default. The actor works without a proxy on normal IPs, and proxy is available if you want to spread load on very large or repeated runs. If IAAI starts returning challenge pages, lowering maxConcurrency to 2 or 3 usually helps more than a proxy.

Can I keep photos out of the output?

Yes. Set includePhotos to false to drop the photo gallery URLs. Photo counts and the thumbnail are still returned.

SEO Keywords

iaai scraper, iaai api, iaai salvage cars, salvage car auction data, copart iaai data, salvage auto auction scraper, insurance auto auctions, vin lookup auction, rebuildable cars data, auto dealer inventory, auction lot data, iaai vehicle detail, salvage title data, odometer data auction, acv data, buy now price auction, copart vs iaai, vehicle auction dataset, car auction api, dealer lead generation, salvage car database, us canada auction data, iaai without api, auto auction price data, rebuilders inventory

For AI Agents & LLM Apps

Purpose: return IAAI salvage and used-vehicle auction lot rows (VIN, damage, title, odometer, ACV, bids, buy-now, branch) for a set of listing/search/lot URLs or a keyword.

Minimal working input:

{ "startUrls": [{ "url": "https://www.iaai.com/Vehiclelisting/Cars/Toyota" }] }

Variant using a keyword with photos off:

{ "keyword": "honda civic", "maxItems": 100, "includePhotos": false }

Output fields: itemId, salvageId, stockNumber, url, title, year, make, model, trim, vin, vinMasked, vinStatus, bodyStyle, exteriorColor, interiorColor, engine, cylinders, fuelType, transmission, driveLineType, displacement, countryOfOrigin, vehicleType, vehicleSubType, vehicleClass, segment, primaryDamage, primaryDamageCode, secondaryDamage, secondaryDamageCode, lossType, lossTypeCode, titleType, titleCode, titleState, titleStateName, titleBrand, saleDocument, odometer, odometerUnit, odometerBrand, keysAvailable, keyFob, airbagState, startsDesc, startsCode, runAndDrive, operable, inventoryStatus, vehicleGrade, whoCanBuy, auctionDateTime, auctionDate, lane, slot, aisle, stall, currency, currentBid, minimumBidAmount, bidIncrement, buyNowPrice, buyNowAvailable, acv, estimatedRepairCost, branchName, market, region, providerGroup, photoUrls, photoCount, thumbnail, image360Url, engineVideoExists, link360, saleHistory, seller, location, scrapedAt, source.

Behaviors an agent should know:

• startUrls takes priority. keyword, category and make are used only when startUrls is empty, and only the first of those that is set builds the URL (keyword first, then make, then category).
• scrapeDetails defaults to true and adds one billed lot-detail event per successfully parsed lot; a failed detail fetch is not billed for that event.
• includePhotos defaults to true and only controls the photo gallery URLs.
• maxItems is capped at 10 for non-paying users; maxPages bounds pagination at 100 lots per page.
• maxConcurrency defaults to 8; IAAI runs bot protection, so lower it to 2 to 3 if challenge pages appear.

Billing: pay-per-event. apify-actor-start (about $0.00005), one apify-default-dataset-item per lot (about $0.001) and one lot-detail per enriched lot (about $0.001), lower at higher loyalty tiers.

Legal & Compliance Disclaimer

This actor is independent and is not affiliated with, endorsed by or sponsored by IAA (Insurance Auto Auctions, Inc.) or its affiliates. It reads only publicly available pages and the public JSON the site itself embeds: it does not log in, does not bypass authentication, does not solve CAPTCHAs and does not place bids.

Users are responsible for complying with IAAI's Terms of Service and with applicable data-protection law in their own jurisdiction. Where the output contains seller, dealer or branch contact data or other personal data, that data must not be used for unsolicited commercial outreach in violation of applicable law.