Drive.com.au Car Listings Scraper (Carsales-compatible) avatar

Drive.com.au Car Listings Scraper (Carsales-compatible)

Pricing

from $1.00 / 1,000 results

Go to Apify Store
Drive.com.au Car Listings Scraper (Carsales-compatible)

Drive.com.au Car Listings Scraper (Carsales-compatible)

Scrape Australian car listings from Drive.com.au. Extracts title, year, make, model, price, odometer, colour, fuel, city, state, images. Carsales.com.au URLs partially supported. HTTP-only, no proxy.

Pricing

from $1.00 / 1,000 results

Rating

5.0

(10)

Developer

Crawler Bros

Crawler Bros

Maintained by Community

Actor stats

11

Bookmarked

1

Total users

0

Monthly active users

9 days ago

Last modified

Share

Carsales.com.au Scraper

Scrape Australian car listings from carsales.com.au.

What this actor extracts

Per listing (when DataDome permits):

  • type, url, listingId, title
  • priceText, priceNumeric, year
  • odometerKm, transmission, fuelType, bodyType, colour
  • sellerType, location, imageUrl, specs
  • scrapedAt

Input

FieldTypeDescription
startUrlsstring[]Carsales URLs (search, brand, detail).
makestringBuild search URL from make if no startUrls.
modelstringModel filter combined with make.
maxItemsintegerMax listings per run.

⚠️ Important: DataDome protection

Carsales.com.au is protected by DataDome, which challenges every fetch with a JavaScript proof-of-work that must be solved in a real browser. This actor uses curl_cffi (Chrome TLS fingerprint) with a rotating Apify RESIDENTIAL proxy pool — but even residential AU/NZ/US sessions frequently hit 403 responses.

When the actor cannot retrieve listings, it emits a single carsales_datadome_blocked sentinel record with the attempted URLs and a description, so you can detect block events and trigger a retry on your end.

For guaranteed scraping, route this actor through a paid anti-bot service (ZenRows, ScrapingBee, ScraperAPI) by providing its proxy URL as the RESIDENTIAL proxy. The actor code will continue to work unchanged.

How it works

  1. Rotate through 5 residential proxy configurations (AU → NZ → US → any → direct).
  2. curl_cffi chrome131 impersonation + organic-traffic-style headers (Google referer, sec-fetch-* cookie set).
  3. Parse listing cards by finding every a[href*="/cars/details/"] anchor and walking up to the nearest sensible container for title, price, image, location.
  4. Detail pages parse <h1>, page text for price / year / odometer / specs.

Limitations

  • 403 rates are high. Expect sub-50% success against DataDome.
  • Advanced filter-to-URL (year range, price range, body type, fuel type) not implemented — user must supply pre-filtered search URLs.
  • No pagination beyond the first page of a startUrl — append ?offset=20 etc. manually.

FAQ

Do I need a proxy? No — RESIDENTIAL is baked in, but it may not bypass DataDome on every run.

Why does my daily test return 0 records? Because DataDome blocked every retry. The actor emits a carsales_datadome_blocked sentinel so the run has non-zero items.