Bid.cars Scraper avatar

Bid.cars Scraper

Pricing

from $1.00 / 1,000 results

Go to Apify Store
Bid.cars Scraper

Bid.cars Scraper

Extract vehicle auction data from Bid.cars. Collect car details, current bids, auction timers, and seller information. Ideal for market analysis, competitive pricing research, and inventory monitoring. Automate your vehicle sourcing workflow.

Pricing

from $1.00 / 1,000 results

Rating

5.0

(4)

Developer

Shahid Irfan

Shahid Irfan

Maintained by Community

Actor stats

1

Bookmarked

29

Total users

6

Monthly active users

18 days ago

Last modified

Share

What does Bid.cars Scraper do?

Bid.cars Scraper collects structured vehicle auction data from Bid.cars search results. Use a Bid.cars search URL, a vehicle keyword, or a location filter to extract vehicle titles, lot numbers, VINs, prices, seller details, damage information, sale documents, auction timers, and media links into an Apify dataset.

This Bid.cars scraper is built for salvage buyers, exporters, dealerships, brokers, vehicle-market analysts, and inventory teams that need repeatable auction data without copying listings by hand. The output can be reviewed in Apify, downloaded as JSON, CSV, Excel, or XML, sent to Google Sheets, or connected to downstream systems through webhooks and the Apify API.

Why use Bid.cars Scraper?

  • Auction inventory monitoring - Track available Bid.cars lots by make, model, year, seller, location, sale document, damage type, and auction status.
  • Vehicle sourcing research - Build shortlists of vehicles that match a sourcing strategy, including salvage, used, buy-now, and active auction listings.
  • Pricing and market analysis - Compare pre-bid prices, final bids, buy-now prices, estimated value ranges, odometer readings, and sale timing across matching vehicles.
  • Cleaner vehicle datasets - Save deduplicated records with empty fields removed, making the dataset easier to review, export, and use in reporting.
  • Automation-ready output - Schedule recurring runs, export datasets, connect webhooks, or retrieve the results through the Apify API for internal tools and dashboards.

What data can you extract from Bid.cars?

Each dataset item represents one Bid.cars vehicle listing. Fields can be empty when Bid.cars does not publish that value for a specific lot.

FieldDescription
titleFull vehicle title shown on the listing
title_shortShorter vehicle title when available
urlDirect Bid.cars lot URL
lotBid.cars lot identifier
tagListing tag used in the lot URL
vinVehicle identification number
yearModel year parsed from the vehicle title
locationAuction or sale location text
sellerSeller name shown on the listing
seller_codeShort seller value when available
seller_trustedWhether the seller is marked as trusted
search_statusListing status from the search results
status_codeNumeric status code when available
sold_beforeWhether the lot was sold previously
loss_typeLoss type label
primary_damagePrimary damage information
start_codeVehicle start condition text
odometerOdometer value
sale_documentUser-facing sale document label
sale_document_stateSale document state or region code
sale_document_statusSale document status label
title_has_lienWhether a lien flag is present
prebid_close_timePre-bid close time text
buy_now_close_timeBuy-now close time text
time_left_secondsRemaining auction time in seconds
time_left_formattedRemaining auction time as display text
prebid_pricePre-bid price as shown on Bid.cars
final_bidFinal bid as display text
buy_now_priceBuy-now price when available
estimated_minMinimum estimated value
estimated_maxMaximum estimated value
has_videoWhether a video link is available
video_urlVideo URL when available
has_360_viewWhether a 360-view link is available
view_360_url360-view URL when available
image_countNumber of collected image URLs
imagesListing image URLs
specsVehicle specification details such as engine, fuel, drive, and transmission codes

How to scrape Bid.cars vehicle data

  1. Open Bid.cars Scraper in Apify Console.
  2. Paste a public Bid.cars search-results URL into url, or leave it empty for a broad default vehicle search.
  3. Optionally add keyword to focus on a make, model, VIN fragment, lot number, seller, damage term, or sale document term.
  4. Optionally add location to keep only vehicles from a matching location such as Long Island, Cleveland, or Jacksonville (FL).
  5. Set results_wanted and max_pages for the size of the run.
  6. Run the Actor, inspect the dataset preview, then export or connect the data to your workflow.

A filtered Bid.cars search URL is the most precise starting point because it carries the filters you already selected on Bid.cars. Keyword and location filters are useful when you want to narrow a broader run after collection.

Input Parameters

ParameterTypeRequiredDefaultDescription
urlStringNoPrefilled Bid.cars search URLPublic Bid.cars search results URL. URL filters are used when provided.
keywordStringNoEmptyOptional post-filter for vehicle title, tag, VIN, lot number, seller, damage, or sale document text.
locationStringNoEmptyOptional post-filter for the listing location text, such as Long Island or Cleveland (OH).
results_wantedIntegerNo20Maximum number of vehicle records to save. Minimum: 1.
max_pagesIntegerNo2Maximum number of Bid.cars result pages to process. Minimum: 1.
proxyConfigurationObjectNo{"useApifyProxy": false}Optional proxy settings for runs that need additional request stability.

Output Data

FieldTypeDescription
titleStringFull vehicle title
title_shortStringShort vehicle title when available
urlStringDirect Bid.cars lot URL
lotStringLot identifier
tagStringURL tag for the lot
vinStringVehicle identification number
yearNumberParsed model year
locationStringSale location
sellerStringSeller name
seller_codeStringSeller code or short seller label
seller_trustedBooleanTrusted seller indicator
search_statusStringSearch-result status
status_codeNumberNumeric listing status
sold_beforeBooleanPrevious sale indicator
loss_typeStringLoss type
primary_damageStringMain damage label
start_codeStringStart condition
odometerNumberOdometer value
sale_documentStringSale document label
prebid_close_timeStringPre-bid close time
buy_now_close_timeStringBuy-now close time
time_left_secondsNumberRemaining time in seconds
prebid_priceStringPre-bid price
final_bidStringFinal bid display value
buy_now_priceStringBuy-now price
estimated_minNumberLower estimated value
estimated_maxNumberUpper estimated value
has_videoBooleanVideo availability
video_urlStringVideo URL
has_360_viewBoolean360-view availability
view_360_urlString360-view URL
image_countNumberNumber of image URLs collected
imagesArrayImage URLs
specsObjectVehicle specification values

Usage Examples

Broad vehicle collection

Collect the first 20 available Bid.cars vehicle listings from the default search scope.

{
"results_wanted": 20,
"max_pages": 2
}

Filtered Bid.cars search URL

Use a Bid.cars URL that already contains your selected make, model, year range, status, and auction filters.

{
"url": "https://bid.cars/en/search/results?search-type=filters&status=All&type=Automobile&make=Toyota&model=Camry&year-from=2018&year-to=2027&auction-type=All",
"results_wanted": 50,
"max_pages": 4
}

Keyword and location narrowing

Collect vehicles matching a model keyword and keep only records from a matching location.

{
"keyword": "Toyota Camry",
"location": "Long Island",
"results_wanted": 30,
"max_pages": 3
}

Proxy-enabled run

Enable Apify Proxy for larger or recurring collection jobs that need additional stability.

{
"url": "https://bid.cars/en/search/results?search-type=filters&status=All&type=Automobile&make=Honda&model=Civic&year-from=2017&year-to=2027&auction-type=All",
"results_wanted": 100,
"max_pages": 5,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": [
"RESIDENTIAL"
]
}
}

Sample Output

{
"title": "2024 Jeep Grand Cherokee, L Laredo",
"title_short": "2024 Jeep Grand Cherokee",
"url": "https://bid.cars/en/lot/1-72412935/2024-Jeep-Grand-Cherokee-1C4RJKAG8R8507951",
"lot": "1-72412935",
"tag": "2024-Jeep-Grand-Cherokee-1C4RJKAG8R8507951",
"vin": "1C4RJKAG8R8507951",
"year": 2024,
"location": "San Diego (CA)",
"seller": "Insurance Company",
"seller_trusted": true,
"search_status": "active",
"primary_damage": "Front end",
"start_code": "Run / Drive",
"odometer": 43427,
"sale_document": "SALVAGE CERTIFICATE (CA)",
"prebid_close_time": "Tue 21 Apr, 13:00 GMT+2",
"prebid_price": "$0",
"estimated_min": 11160,
"estimated_max": 17270,
"has_video": true,
"video_url": "https://cs.copart.com/v1/AUTH_svc.pdoc00001/ids-c-prod-lpp/0126/example.mp4",
"has_360_view": true,
"view_360_url": "https://bid.cars/app/lot/1-72412935/three-sixty-view",
"image_count": 21,
"images": [
"https://pluto.bid.car/1-72412935/example-1.jpg",
"https://images.bid.cars/172412935_example/example-2.jpg"
],
"specs": {
"key_info": "Present",
"transmission_code": 0,
"fuel_type_code": "0",
"drive_type_code": 2,
"engine": "3.6L, V6, 293HP"
}
}

Tips for best results

  • Start from a real Bid.cars search - Apply filters on Bid.cars first, then copy the full search-results URL into url.
  • Keep test runs small - Start with results_wanted: 20 and max_pages: 2, then increase limits after checking the dataset.
  • Use focused filters - Narrow by make, model, year range, auction status, location, or sale document when you need a comparable vehicle set.
  • Use keyword filtering for review queues - Search for a model, VIN fragment, seller name, damage label, or lot number when you need a smaller subset.
  • Expect optional fields - Images, videos, 360 views, sale document details, and pricing fields depend on what Bid.cars publishes for each lot.
  • Schedule stable searches - Reuse the same filtered URL for recurring inventory snapshots and price monitoring.
  • Report source changes - Public listing pages can change. If a saved search stops returning expected fields, report the issue through the Actor Issues tab with the affected URL.

Integrations

  • Google Sheets - Export Bid.cars vehicle data for review, filtering, and team analysis.
  • Airtable - Build searchable auction inventory databases.
  • Webhooks - Send completed run data to internal systems, alerts, or data pipelines.
  • Make or Zapier - Add new vehicle records to no-code workflows.
  • Apify API - Retrieve datasets programmatically for dashboards, databases, and AI agents.

Export formats

  • JSON - Use structured records in applications, scripts, and APIs.
  • CSV - Analyze listings in spreadsheets and BI tools.
  • Excel - Share vehicle datasets with non-technical teams.
  • XML - Feed results into systems that use XML exchange formats.

Frequently Asked Questions

Can I use a Bid.cars search URL?

Yes. A Bid.cars search results URL is the best way to preserve the exact filters you selected on the website.

Can I collect Bid.cars listings without a URL?

Yes. Leave url empty to use the default broad vehicle search, then use keyword or location when you need a narrower dataset.

Can I filter by VIN, lot number, seller, or damage?

Yes. Use keyword to match text across vehicle title, tag, VIN, lot number, seller, loss type, primary damage, and sale document fields.

Are duplicate Bid.cars listings removed?

Yes. Listings are deduplicated within each run before they are saved to the dataset.

Why are some Bid.cars fields missing?

Some fields are missing because the source listing did not publish that information. Empty and placeholder values are removed so the dataset stays cleaner.

Can I export Bid.cars data to CSV or Excel?

Yes. Apify datasets can be downloaded in CSV, Excel, JSON, XML, and other supported formats after the run finishes.

Can I run Bid.cars Scraper on a schedule?

Yes. You can schedule the Actor in Apify Console to refresh vehicle datasets hourly, daily, weekly, or at another interval.

Is this Actor suitable for non-technical users?

Yes. You can paste a search URL, set a result limit, run the Actor from the form-based input, and download the completed dataset without writing code.

Scraping public web data can be lawful, but you are responsible for complying with applicable laws, Bid.cars terms, privacy obligations, and any restrictions that apply to your use of the data.

  • Copart Vehicle Auction Scraper πŸš— - Collect live Copart vehicle auction listings with VINs, bids, lot details, damage, locations, and images.
  • IAAI Vehicles Scraper πŸš— - Extract IAAI vehicle auction listings with specifications, pricing, sale timing, damage, and branch details.
  • Cars.com Scraper - Collect public Cars.com vehicle listings with prices, mileage, VINs, dealer details, images, and listing URLs.
  • Cinch.co.uk Vehicle Scraper - Extract UK used-car listings with prices, mileage, specifications, dealer site details, images, and finance data.

Support

For issues, feature requests, or custom Actor work, use the Issues tab on the Bid.cars Scraper page or contact the developer through Apify.

Bid.cars Scraper is intended for legitimate collection of publicly available vehicle-listing data. Users are responsible for using the data responsibly and complying with applicable laws, Bid.cars terms, privacy requirements, and website policies.