Auction scraping

We parse Copart and IAAI lots into a structure your team can search, score and enrich. Other auction sources, in the US, Korea or Europe, are added as custom parsers per engagement.

Custom parsers for auction formats, listing pages, and lot feeds.

Vehicle, image, bid, sale, and condition fields normalized for your workflow.

Source coverage planned around your target markets and update cadence.

How the pipeline works

• We write a parser per source rather than one generic crawler. Auction listing pages differ in structure, in how they publish bids and in what they withhold, and a parser tuned to the source is what keeps the field set complete.
• Extracted records are normalized onto one schema: the vehicle, its images, the bid and sale history, and the condition fields, carrying the same names and the same units no matter which auction the row came from.
• Coverage and update cadence are agreed per engagement. A source refreshed hourly and a source refreshed nightly cost differently, and which lots are worth refreshing at all depends on the markets you buy in.

What the feed gives you

• Copart and IAAI are live in the lots API today. US, Korean, European and other sources are built as custom parsers around your target markets; adding one is parser work, not a configuration switch, so the list grows with the engagement.
• Vehicle, image, bid, sale and condition fields, normalized so that a query does not have to branch per source.
• An update cadence set per source, because a fresh-arrivals feed and an archive backfill are two different jobs with two different costs.
• Records can be enriched with Partsify damage detection inside the same pipeline, so a scraped lot arrives already scored rather than waiting on a second pass.

Who it fits

Teams that already know what they want to do with auction data — rank it, price it, resell it — and are losing engineering time to parsers that break every time a source changes its markup.

It is the wrong tool if you need a handful of lots looked up by hand. The free lot tools on this site answer that question today, without a contract and without an integration. Scraping is worth its setup only when the same question is asked of thousands of lots on a schedule.

Lots API

Scraped Copart and IAAI lots can be queried on api.partsify.io with the same API key. Other auction sources are built as custom parsers per engagement.

• GET /api/v1/lots Searches lots by source, make, model, lot number, VIN, year, body style, fuel type, transmission, drivetrain, condition, primary damage, odometer, price, sale date, location or free text. Sorts by sale date, price, year, odometer or last seen, up to 100 lots per page.
• GET /api/v1/lots/facets Counts how many lots match each source, make, model, fuel type, transmission, drivetrain, body style, condition and primary damage under the same filters, ready for a filter panel.
• GET /api/v1/lots/{lot_id} Returns one lot with all of its photos and the dates it was first and last seen.

Fields on every lot

VIN, make, model, year, body style, fuel type, transmission, drivetrain, odometer, condition, primary and secondary damage, location, horsepower, engine capacity, current bid, buy-now price, price, sale date, primary photo and photo count.

Full schema and a live console: api.partsify.io/docs

Tell us what volume, sources, and workflow you need.

Share your auction sources, report volume, API needs, or website goals. We will route the request and follow up with the right next step.

Does Partsify inspect hidden structural damage?

No. A remote report cannot replace a physical teardown, and Partsify does not claim to detect hidden structural, frame or mechanical damage. It reads the auction photos for visible damage, then names the likely replacement parts with OEM numbers and current supplier prices, estimates labor hours, and totals the repair before you bid.

Partsify is operated by SCRAPEX LTD, Limassol, Cyprus. The interactive report tool requires JavaScript. Legal Information · Contact Us · Blog