Copart Public Search Scraper

Copart Public Search Scraper returns public Copart auction lots as clean, structured vehicle records: lot number and URL, year, make, model, masked VIN, current bid, estimated retail value, damage, scheduled sale date, yard location and a thumbnail image. It is intended for auction inventory research, sourcing, price comparison, and workflow automation—not for logging in, bidding, payment, watchlists, or accessing non-public data.

What it returns

Each dataset item represents one unique public lot. The actor returns lotNumber, lotUrl, vehicle year/make/model, VIN as publicly shown (Copart masks the last digits), current bid, estimated retail value, damage, sale date, location, a thumbnail image URL, the source search URL, and an ISO 8601 collection timestamp. Optional values are returned as null so the shape is stable for API and AI-agent workflows. saleDate is filled only when Copart publishes a scheduled auction date for the lot, and estimatedRetailValue is null when Copart shows no value.

When to use it

Use it with the featured vehicle finder, a Copart keyword search URL (the query parameter, for example https://www.copart.com/lotSearchResults?free=true&query=toyota), or a direct public lot URL. The keyword is applied; other filters selected on the Copart page (year, damage, yard) are not, so filter the dataset afterwards. Lots are deduplicated by lot number.

Do not use it for Copart login, member, payment, bidding, saved-search, watchlist, or other authenticated URLs. It does not provide account access, bypass access controls, or take auction actions.

Input

startUrls accepts one or more public URLs. When it is empty, the Actor uses the public featured vehicle finder. maxResults caps results from 1 to 200, including the billable maximum. maxRequestRetries controls temporary-failure retries and is deliberately capped at three.

Example input:

{
  "startUrls": [{ "url": "https://www.copart.com/vehicle-search-featured/vehicleFinder" }],
  "maxResults": 25,
  "maxRequestRetries": 2
}

Output example

{
  "lotNumber": "99714325",
  "lotUrl": "https://www.copart.com/lot/99714325",
  "year": 2019,
  "make": "TOYOTA",
  "model": "CAMRY",
  "vin": null,
  "currentBid": 4250,
  "estimatedRetailValue": 12450,
  "primaryDamage": "FRONT END",
  "saleDate": null,
  "location": "PA - PITTSBURGH SOUTH",
  "imageUrls": [],
  "searchUrl": "https://www.copart.com/vehicle-search-featured/vehicleFinder",
  "scrapedAt": "2026-07-22T12:00:00.000Z"
}

Pricing

This Actor uses pay-per-event pricing. These are the current Apify Store event prices:

Event	Price (USD)	When it is charged
lot-scraped	FREE $0.016001; BRONZE $0.0156; SILVER $0.0152; GOLD/PLATINUM/DIAMOND $0.0128	Once for each unique public Copart lot written to the dataset.
apify-actor-start	FREE $0.006251; BRONZE $0.006094; SILVER $0.005938; GOLD/PLATINUM/DIAMOND $0.005	Once per run per GB of memory (default 512 MB, so one event).

Example on the FREE tier: 25 lots cost about $0.40 in lot events plus one start event. A lot is charged only after it is written to the dataset, and the run stops cleanly before writing a lot that the run's maximum charge cannot cover.

Apify platform usage for this Actor run is included alongside the event prices above; no separate per-run platform-usage fee is passed to users.

This covers Apify platform usage for this Actor run. Other Apify products or usage outside this Actor run may still follow your account plan.

Reliability and limits

Requests use an owner-managed residential access route. If it is not configured, the run stops with a configuration error before any target request and charges no lots; no credential is ever part of the Actor input or dataset.

Copart can change public-page structure or temporarily limit automated traffic. The actor uses conservative retries, keeps valid no-results searches successful, and reports all-request public-access failures honestly instead of silently producing an empty dataset. For repeat research workloads, use reasonable result limits and respect Copart's terms and applicable law.

FAQ

Which Copart URLs work? The featured vehicle finder, keyword search URLs with a query parameter, and individual lot URLs on copart.com, copart.ca, copart.co.uk, copart.de or copart.ie.

Are filters from my Copart search applied? Only the keyword. Year, make, damage and yard filters selected on the Copart page are not applied; filter the dataset after the run.

How many lots can one run return? Up to 200 unique lots per run (maxResults).

Why is saleDate empty for some lots? Copart has not scheduled an auction date for those lots yet.

Am I charged when nothing is found or the site blocks the run? No lot events are charged. A run where every request fails ends as failed; only the start event applies.

API and AI-agent use

This actor has a narrow input contract and a stable flat output shape for Apify API and MCP users. Use it for public auction-inventory research. Do not use it as a vehicle-history, private-account, bidding, or title-verification tool.

Compliance

You are responsible for confirming that your collection and use of public data comply with Copart terms, applicable law, and your own authorization. Do not submit credentials or attempt to use this actor to access non-public content.

Last verified: 2026-10-27