EnglishCar data guides for developers
For engineers building catalogs, VIN pages and pricing tools on auction and marketplace data: the APIs, the sync loop that keeps a catalog fresh and the parts that usually break.
For developersCopart API: what data you can get and how to get it
Copart has no open data API for third parties. Here is what Copart data you can get, the realistic options, and what requests and records look like.
For developersIAAI API: getting Insurance Auto Auctions data into your app
IAAI has its own vocabulary: stock numbers, item IDs, branches, start codes, timed auctions. How each maps to API fields, with requests and a full record.
For developersCopart scraper or API: what scraping Copart really costs
A Copart scraper takes a day to write and years to keep alive. What it needs, where it breaks, how its cost is built, and when building one is still the right call.
For developersDecoding VINs with the free NHTSA vPIC API: a practical guide
The free NHTSA vPIC API in practice: which calls to use, what ErrorCode means, which fields are often empty, how to batch 50 VINs and cache the results.
For developersHow to build a car auction website like bid.cars
What sites like bid.cars and stat.vin are made of, the architecture behind them, the parts that take longest and a phased plan to build one.
For developersSync car auction data: an hourly import that doesn't break
A tutorial for an hourly sync of Copart and IAAI lots: the first import, two feeds per hour, upserts by lot, archiving sold lots, retries and monitoring.How these guides are written and checked: editorial standards. New articles by RSS.