Copart Scraper

Collect structured vehicle-auction records from Copart lot and search URLs. Very high data coverage: up to 29 fields are available for each product.

Issues and feature requests

If you encounter an issue or need a field added, open an issue on the Actor page or write to hello@123webdata.com.

For custom requirements, you can also reach out to us by filling this form.

Output Example (simplified)

The overview shows the most useful fields in a table. Product images are displayed as thumbnails when the website provides them.

Image	Product URL	Product ID	Product name	Current price	Currency	In stock	Brand	Seller	Scraped at
	https://www.copart.com/lot/86148905	86148905	2019 MERCEDES-BENZ E AMG 53 4MATIC	13700	CAD	false	MERCEDES-BENZ	Recovery Hub	2026-08-20T13:43:53.092Z

How to scrape supported list pages

This Actor accepts individual product links in productUrls. It accepts search result pages in categoryUrls.

1. Open a supported list page in your browser.
2. Run a search you need.
3. Copy the final URL from the address bar and paste it into categoryUrls.

The Actor follows the products shown on that page.

Add one or more List URLs to scrape. categoryUrls is labelled List URLs in the Console and accepts search result pages.

Scrape Copart Search Pages

Pass a search results URL and the Actor collects the products that match your query. Example: https://www.copart.com/lotSearchResults?query=ford

The scrapeProductDetails option (labelled Include product details) decides what each List URL produces. When it is enabled, the Actor visits each product page and returns the full detail records; when it is disabled, the Actor returns one list-level record per product card with the fields that are always included.

Features

• Scrapes detailed vehicle auction information from Copart product pages
• Accepts individual product URLs and search result pages
• Lets you limit the number of saved products and choose whether to continue through additional result pages
• Returns structured current bids, vehicle specifications, damage details, auction timing, and photo galleries for viewing, export, and analysis

Pricing

This Actor uses pay-per-event pricing. Its running costs are included.

• Actor start: $0.02 once per run — One fixed charge for starting a run.
• Result: $0.00089 each ($0.89 per 1,000) — A product record collected directly from a supported list page.
• Product detail: $0.00199 each ($1.99 per 1,000) — A full product record collected from its product page.

The start charge applies once per run. Each saved product is charged either as a Result or a Product detail, never both.

Results in one run	Result	Product detail
100	$0.11	$0.22
1,000	$0.91	$2.01

Apify's Free plan currently includes $5 in monthly usage credits. If the full $5 is available for this Actor, one run covers about 5,595 Results or 2,502 Product details. Other Apify usage reduces the available credit.

Input

The Actor accepts the following input parameters:

Field	Type	Description
productUrls	array	Product URLs to scrape
categoryUrls	array	Supported list pages: search result pages
maxResultsPerScrape	integer	Maximum number of product records to save
usePagination	boolean	Whether to continue through additional result pages
scrapeProductDetails	boolean	If the Include product details option is enabled, the Actor visits each product page for the full detail record; if it is disabled, the Actor returns one list-level result record per product card. Both field lists are in "What data you get in each mode" below.

What data you get in each mode

Every saved product is stored as one record. scrapeProductDetails decides which mode you receive; the lists below name every field each mode can return. A field is empty when the website does not show that information.

Result

A list-level product record with 29 declared fields:

url, product_id, name, price, currency, in_stock, sku, brand, category, main_image, images, color, features, attributes, seller_name, canonical_url, scraped_at, buy_now_price, current_bid, estimated_retail_value, location, odometer, odometer_status, primary_damage, sale_date, sale_status, secondary_damage, vin, year

Product detail

A full product record with 29 declared fields:

url, product_id, name, price, currency, in_stock, sku, brand, category, main_image, images, color, features, attributes, seller_name, canonical_url, scraped_at, buy_now_price, current_bid, estimated_retail_value, location, odometer, odometer_status, primary_damage, sale_date, sale_status, secondary_damage, vin, year

Output Example (full)

The Actor stores one structured record per product. Card-only records contain only fields available on the list; detail-only fields are omitted.

{
  "url": "https://www.copart.com/lot/86148905",
  "product_id": "86148905",
  "name": "2019 MERCEDES-BENZ E AMG 53 4MATIC",
  "price": 13700,
  "currency": "CAD",
  "in_stock": false,
  "sku": "86148905",
  "brand": "MERCEDES-BENZ",
  "category": "Vehicle Auctions",
  "main_image": null,
  "images": [],
  "color": "BLUE",
  "features": [
    "RUNS AND DRIVES",
    "AUTOCHECK",
    "CERT-D",
    "IV",
    "SITE-CA"
  ],
  "attributes": {
    "Engine": "3.0L 6",
    "Transmission": "AUTOMATIC",
    "Drivetrain": "ALL WHEEL DRIVE",
    "Fuel": "GAS",
    "Keys": "YES",
    "Title": "ON"
  },
  "seller_name": "Recovery Hub",
  "canonical_url": "https://www.copart.com/lot/86148905",
  "scraped_at": "2026-08-20T13:43:53.092Z",
  "buy_now_price": null,
  "current_bid": 13700,
  "estimated_retail_value": null,
  "location": "QC - MONTREAL",
  "odometer": 63654,
  "odometer_status": "ACTUAL",
  "primary_damage": "NORMAL WEAR",
  "sale_date": "2026-08-19T17:00:00.000Z",
  "sale_status": "ON_APPROVAL",
  "secondary_damage": "MINOR DENT/SCRATCHES",
  "vin": "WDDZF6BB0KA******",
  "year": 2019
}

Use Cases

• Track current vehicle auction bids and buy-it-now offers
• Compare vehicle specifications, damage, and yard locations
• Build reproducible salvage and wholesale vehicle datasets

You might also like

• Our other used car marketplace scrapers
• Our other auction scrapers
• Cars & Bids Scraper
• Bring a Trailer Scraper
• AutoScout24 Scraper

Integrate with AI and automation

Use with AI through MCP

Connect your AI assistant to the Apify MCP server. It can discover and run Actors, then access the results in the same conversation. For example, ask your assistant to scrape a list of products from Copart, compare prices, or summarize the collected data.

Run on a schedule

After one successful run, use Apify Schedules to repeat the same task hourly, daily, weekly, or with a custom cron schedule. Saved tasks are useful when you want to keep the same URLs and settings for every run.

Connect with n8n

Create an n8n account and add the verified Apify node to a workflow. Choose Run an Actor and Get Dataset when the workflow should start this Actor, wait for completion, and receive the product rows for the next node. See the Apify integration for n8n.

Connect with Make

Create a Make account and add the Apify Run an Actor module. Follow it with Get Dataset Items to pass the product rows to Google Sheets, a database, email, or another Make module. For longer runs, use Watch Actor Runs followed by Get Dataset Items.

Read the Make integration guide.