Copart Auction Scraper — Direct API · Damage & Bid Data avatar

Copart Auction Scraper — Direct API · Damage & Bid Data

Pricing

from $0.005 / actor start

Go to Apify Store
Copart Auction Scraper — Direct API · Damage & Bid Data

Copart Auction Scraper — Direct API · Damage & Bid Data

Scrape Copart vehicle auctions via direct API: VIN, damage, odometer, estimated value, repair cost, current bid, buy-it-now price and auction date. Search by keyword or lot URL, no browser needed.

Pricing

from $0.005 / actor start

Rating

0.0

(0)

Developer

Gio

Gio

Maintained by Community

Actor stats

0

Bookmarked

5

Total users

0

Monthly active users

7 days ago

Last modified

Features

Limited permissions

Share

Copart Auction Scraper — Direct API · Damage, Bid & Repair Cost

Why use this scraper

Copart is the largest online vehicle auction platform in the world, listing salvage, clean-title and insurance-total-loss vehicles by the hundreds of thousands across 8+ countries. Dealers, dismantlers, exporters and vehicle-history services all need this data in bulk: damage type, odometer reading, estimated retail value, current bid and repair cost, to price arbitrage opportunities before an auction closes. Copart has no public bulk-export API for this, and its search page is a JavaScript application that most scrapers have to render in a full browser, which is slow and easy to get blocked.

This actor skips the browser entirely. It calls the same internal JSON API that Copart's own search page calls in the background, and returns full, structured lot data directly: no screenshots, no CSS selectors, no headless Chrome to keep alive. You give it a search keyword or a Copart URL and get back every lot's auction details as clean JSON, ready to filter, sort or load into a spreadsheet.

Overview

The actor searches Copart's public lot database by keyword (the same text you would type into Copart's own search bar) or reads specific lot numbers from direct lot URLs. For each lot it returns year, make, model, VIN (as publicly exposed, see Notes below), primary and secondary damage, odometer reading and brand, estimated retail value, repair cost, current bid, buy-it-now price, title state and code, color, drivetrain details, key status, sale status, location, auction date and a thumbnail image URL. A single keyword search can return up to 100 lots per page, with automatic pagination and de-duplication by lot number up to your maxItems limit.

Supported inputs

  • Keyword search: pass any search term the way you would type it into Copart's own search bar ("tesla", "ford f-150 damage front", "harley"). The actor ranks results the same way Copart's own search does.
  • Copart search URL: paste a full copart.com/lotSearchResults/?... URL (copied from your browser after applying filters on the Copart site) into startUrls, and the actor reproduces that exact search, filters included.
  • Direct lot URL: paste one or more copart.com/lot/<lotNumber> URLs into startUrls to fetch just those specific lots.
  • maxItems: caps the total number of lots returned. Set to 0 for no cap (the actor will page through all matching results).

Use cases

  • Salvage sourcing for dealers and dismantlers: pull every lot matching a make/model/damage combination to find vehicles worth buying for parts or repair-and-resell.
  • Price arbitrage: compare estimatedRetailValue against currentBid across a batch of lots to flag undervalued auctions before they close.
  • Export-market sourcing: many Copart buyers export salvage vehicles; this actor covers Copart's US and international sites, so a single keyword search can surface lots across multiple country sites at once.
  • Vehicle-history and valuation feeds: feed vin, odometer and primaryDamage into a vehicle-history or valuation database to flag salvage-titled VINs automatically.
  • Auction-date tracking: run this on a schedule against saved searches to get notified the moment a lot you are watching gets a new auctionDate or sale status.

How it works

Copart's search results page is rendered by a single-page JavaScript application, but the data itself comes from a JSON search API that the page calls after it loads. This actor calls that same API directly with the keyword or filters you provide, which means it gets the full structured record for every lot (not just what is visible on screen) without paying the cost of loading a browser, waiting for JavaScript, or scrolling to trigger lazy-loaded results. For a single lot URL, the actor calls Copart's lot-detail API directly rather than parsing the rendered page.

Input configuration

1. Simple keyword search:

{
"searchQuery": "tesla model 3",
"maxItems": 50
}

2. Keyword with no cap (all matching lots):

{
"searchQuery": "harley davidson",
"maxItems": 0
}

3. A saved Copart search URL (filters already applied on copart.com):

{
"startUrls": ["https://www.copart.com/lotSearchResults/?free=true&query=ford%20f-150"],
"maxItems": 100
}

4. One or more specific lots:

{
"startUrls": [
"https://www.copart.com/lot/41750776",
"https://www.copart.com/lot/41760756"
]
}

Output sample

Real lots from a run against the keyword "tesla" on 14 November 2026:

[
{
"lotNumber": "39269024",
"year": 2022,
"make": "TESLA",
"model": "MODEL Y",
"vin": "7SAYGDEF8NF******",
"title": "2022 TESLA MODEL Y",
"primaryDamage": "FRONT END",
"secondaryDamage": "SIDE",
"odometer": 0,
"odometerBrand": "N",
"estimatedRetailValue": 43327,
"repairCost": 41820.96,
"currentBid": 500,
"buyItNowPrice": null,
"currency": "USD",
"color": "WHITE",
"transmission": "AUTOMATIC",
"fuelType": "ELECTRIC",
"titleState": "GA",
"titleCode": "CERT-E, IV, NLC",
"keys": "EXEMPT",
"runsAndDrives": "ENHANCED VEHICLES",
"location": "GA - AUGUSTA",
"saleStatus": "MINIMUM_BID",
"auctionDate": "2024-01-18T08:00:00.000Z",
"imageUrl": "https://cs.copart.com/v1/AUTH_svc.pdoc00001/lpp/0124/504d44a8a9f14b3da32289cc5bee0c00_thb.jpg",
"url": "https://www.copart.com/lot/39269024"
}
]

Key output fields

FieldTypeDescription
lotNumberstringCopart lot number
year, make, modelstring/intVehicle identification
vinstringVIN as publicly exposed by Copart (last characters masked for non-members, see Notes)
primaryDamage, secondaryDamagestringDamage categories reported by Copart
odometer, odometerBrandint/stringMileage and odometer status code (actual, not actual, exempt)
estimatedRetailValuenumberCopart's estimated pre-damage retail value
repairCostnumberCopart's estimated repair cost
currentBid, buyItNowPricenumberLive bid and (if offered) buy-it-now price
color, transmission, fuelType, driveTypestringVehicle spec fields
titleState, titleCodestringTitle jurisdiction and code (salvage, clean, etc.)
keysstringKey availability status
runsAndDrivesstringWhether the lot is tagged as running/driving
locationstringCopart yard name and state
saleStatusstringCurrent sale/auction status
auctionDate, auctionTimestringScheduled auction date and time
imageUrl, urlstringThumbnail photo and direct lot link

Pricing

ActorPrice model
This actor (gio21/copart-scraper)$0.005 per run start + $0.0144–$0.0234 per lot (tiered by plan)
memo23/copart-scraper$0.009 per run start + $0.00075 per lot + $0.001 additional-data fee
parseforge/copart-public-search-scraper$0.0089–$0.01 per run start + $0.0128–$0.026 per lot (tiered)

What makes this richer than the competition

memo23/copart-scraper ("Copart Auction Scraper — Salvage Lots in 8 Countries", 42 users/30 days) is the cheapest per lot of the three ($0.00075/lot plus a small additional-data fee), and is the established leader for this target with the most users. If pure per-lot cost at high volume is your only concern, it is worth comparing directly.

parseforge/copart-public-search-scraper ("Copart Public Search Scraper", 31 users/30 days) sits in a similar price band to this actor.

This actor's advantage is in what each call returns: a single request gives you the full lot profile (VIN, both damage fields, odometer brand, estimated retail value, repair cost, current bid, title code, key status, drivetrain and fuel type) by calling Copart's own internal search and lot-detail API directly, the same one Copart's site itself uses, so field coverage tracks Copart's own data model rather than a hand-maintained scraping template. If you need the technical and condition profile of each lot alongside the bid, not just price and location, this is built around that.

Notes & limitations

  • VIN masking: Copart masks the last characters of the VIN for anyone not logged in as a Copart member (the public search already shows VINs this way, this actor cannot unmask what Copart itself hides). Treat vin as a partial identifier unless you have a Copart member account feeding different URLs.
  • Residential proxy recommended: Copart can rate-limit or block requests from datacenter IPs. The actor's proxyConfiguration input defaults to residential proxy for this reason; leaving it on is recommended.
  • Pagination: maxItems: 0 pages through every result for very broad keywords (e.g. a common make with no model filter), which means more requests and more time. Narrow the keyword for faster, cheaper runs.
  • Non-English fields: on some country sites, titleCode, location and similar fields may come back in the local language rather than English, since the actor returns Copart's data as-is rather than translating it.
  • No live bidding or purchase actions: this actor only reads public lot data. It does not place bids, register you as a buyer, or interact with Copart's account system in any way.

FAQ

Is this affiliated with or endorsed by Copart? No. This is an independent data-extraction tool. See the Disclaimer below.

Why is the VIN partially masked? Copart itself masks the last VIN characters on its public search for anyone without a logged-in Copart member account. The actor returns exactly what Copart's API exposes publicly, it does not have access to unmasked VINs.

Can I filter by damage type, year or auction location? Yes, two ways: include the filter terms in your keyword (e.g. "2020 tesla front end damage"), or apply the filters on copart.com directly, copy the resulting search URL, and pass it as a startUrls entry.

Does this work for Copart sites outside the US? Yes. Copart operates auction sites in multiple countries and the same keyword-search approach works across them; results depend on what Copart's own search surfaces for that query.

What happens if a lot has already sold or been removed? A removed or expired lot URL returns a warning for that lot rather than failing the whole run; all other lots in the same run are unaffected.

How current is the current bid data? currentBid reflects Copart's data at the moment the actor made the request. For live-auction lots, bids can change within seconds, treat the field as a snapshot, not a live feed.

For AI Agents & LLM Apps

This actor is callable directly from an MCP client (Claude, Cursor, or any MCP-compatible agent) via mcp.apify.com, or from any HTTP client via the Apify API's run-sync-get-dataset-items endpoint:

POST https://api.apify.com/v2/acts/gio21~copart-scraper/run-sync-get-dataset-items
Content-Type: application/json
{
"searchQuery": "tesla model 3",
"maxItems": 20
}

The response is a plain JSON array of lot records, ready for an LLM to filter by damage type, rank by estimated-value-to-bid ratio, or summarize for a buyer.

Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Copart or any of its subsidiaries. All trademarks mentioned are the property of their respective owners.

SEO Keywords

Copart scraper, Copart auction scraper, Copart API, Copart salvage scraper, scrape Copart, Copart lot data, Copart VIN scraper