Autotrader UK and Canada Data: Used Car Prices, Mileage and Dealer Contacts
Pull Autotrader UK and AutoTrader.ca listings into one sheet with price, mileage, specs and dealer phone, for pricing work, stock checks and dealer lead lists.
The actor referenced in this article. Pay only for results delivered.
If you price used cars for a living, you already know the problem. Autotrader UK and AutoTrader Canada show you a page of 20 cars at a time, the price filter hides the spread you actually want to see, and there is no button that turns a search into a spreadsheet. A dealer checking how a rival prices a three year old BMW, an analyst tracking how mileage pulls a model’s price down, and a sales team building a list of independent dealers in one region all end up copying listings by hand, and the copy is out of date by the next morning.
Try it live: Autotrader Scraper. Pay per result delivered.
The Autotrader Scraper reads the public search results and listing pages of both sites and returns one flat row per car. You can describe the search in plain fields (make, model, postcode or city, price, year, mileage, fuel, gearbox, body, seller type) or paste a results link you already built on the site, and every filter in that link is kept. The UK and Canadian rows share one shape, with country, currency (GBP or CAD) and mileage_unit (miles or km) on every row, so both markets fit in one sheet.
Which car actor fits which job
The Mine Works has car listing actors for four markets. They differ by market more than by method:
| Job | Market | Actor |
|---|---|---|
| UK used car prices, dealer stock and dealer contacts | United Kingdom | Autotrader Scraper |
| Canadian used car prices and dealers, by city and radius in km | Canada | Autotrader Scraper |
| Listings across eight European countries with dealer contact | Europe | AutoScout24 Scraper |
| German listings with gross and net price, VAT and dealer contact | Germany | mobile.de Scraper |
| Australian listings with price in AUD and odometer in km | Australia | Carsales.com.au Scraper |
If you compare prices for the same model across markets, run the actors side by side and join on make, model and year. This post covers the Autotrader one.
Three inputs for three jobs
Price analysis: one model in one region
This is the search a pricing analyst runs first. It returns automatic Volkswagen Golfs from 2018 or later, under £15,000, within 40 miles of central Manchester, cheapest first:
{
"country": "UK",
"make": "Volkswagen",
"model": "Golf",
"postcode": "M1 1AE",
"radius": 40,
"yearMin": 2018,
"priceMax": 15000,
"transmission": "automatic",
"sort": "price_asc",
"maxResults": 200
}
With includeDetails left on (the default), each car’s own page is read too. That adds fuel, gearbox, body, colour, engine size and power, doors, seats, owners, the history check, the full description and every photo. It also fills price_indicator and price_vs_market, the site’s comparison of the price with the market average.
Canada: one model around one city
For AutoTrader Canada, switch country to CA and give a city with its province instead of a postcode. The radius is then in kilometres:
{
"country": "CA",
"make": "Honda",
"model": "CR-V",
"location": "Toronto, ON",
"radius": 100,
"maxResults": 200
}
Prices come back in CAD and mileage in km. Canadian rows also carry province.
Dealer lead list: trade sellers around one postcode
For a lead list you want volume more than the full spec, so turn the listing page off and keep dealers only:
{
"country": "UK",
"postcode": "B1 1AA",
"radius": 30,
"sellerType": "dealer",
"includeDetails": false,
"maxResults": 2000
}
One thing to know before you run this. UK result cards do not carry the dealer name, fuel, gearbox or body; those come from the listing page. So for a UK lead list where you need the dealer’s name, phone and address on every row, leave includeDetails on and accept the slower run. Canadian cards already carry fuel, gearbox and the dealer name, so includeDetails: false works better there. The price per car is the same either way.
A Python example: median price by year, plus the dealer list
This script pulls 500 dealer listings for one model, prints the median price and median mileage for each model year, then prints one line per dealer. Rows with a _type field are the summary, info and error rows, which are never charged; skip them.
from statistics import median
from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("themineworks/autotrader-scraper").call(run_input={
"country": "UK",
"make": "BMW",
"model": "3 Series",
"postcode": "SW1A 1AA",
"radius": 50,
"sellerType": "dealer",
"sort": "most_recent",
"maxResults": 500,
})
by_year = {}
dealers = {}
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
if item.get("_type"):
continue
if item.get("price") and item.get("year"):
by_year.setdefault(item["year"], []).append(item)
if item.get("dealer_id"):
dealers.setdefault(item["dealer_id"], item)
for year in sorted(by_year):
cars = by_year[year]
prices = [c["price"] for c in cars]
miles = [c["mileage"] for c in cars if c.get("mileage")]
print(year, len(cars), "cars, median price", median(prices),
"median mileage", median(miles) if miles else None)
for d in dealers.values():
print(d.get("dealer_name"), d.get("dealer_phone"), d.get("dealer_postcode"), d.get("dealer_rating"))
Swap the print calls for a write to Google Sheets or a database and you have a weekly price table. Schedule the same input daily with sort: "most_recent" and compare runs on listing_id to keep only new cars, or to spot a lower price on a car you saw last week.
What one row holds
| Group | Fields |
|---|---|
| The car | listing_id, url, title, make, model, variant, year, registration, first_registered, condition |
| Price | price, price_text, currency, price_indicator, price_vs_market |
| Use and spec | mileage, mileage_unit, fuel_type, transmission, body_type, colour, engine_size_litres, engine_power, drivetrain, doors, seats |
| History (UK) | owners, history_check, write_off_category |
| Dealer | seller_type, dealer_id, dealer_name, dealer_address, dealer_town, dealer_postcode, dealer_phone, dealer_rating, dealer_review_count, dealer_url |
| Place | location, province, distance, distance_unit |
| Media and source | image_url, images, image_count, description, search_label, page, position, scraped_at |
For a pricing model, price, year, mileage, fuel_type, transmission and variant are the columns that do most of the work. For a lead list, group on dealer_id and count cars per dealer: a dealer with 60 cars in stock is a different conversation from one with six. The README’s sample row is a 2012 BMW 320i M Sport convertible at £2,495 with 71,000 miles, marked “Lower price” and “£2,710 below market average”, from a dealer in Wembley with a 4.9 rating.
If you also want the dealers’ websites and email addresses, the B2B lead generation stack shows how to enrich a list of business names and towns, and Maps Leads covers pulling verified emails from Google Maps listings.
Price, exactly
Pay per event. Two events are charged:
| Event | When | Free plan | Bronze | Silver | Gold and above |
|---|---|---|---|---|---|
car-listing | Once per car row stored in your dataset | $0.81 per 1,000 | $0.80 per 1,000 | $0.79 per 1,000 | $0.78 per 1,000 |
run-start | Once per run, after a search returned cars | $0.003 | $0.003 | $0.003 | $0.003 |
The source code confirms the start fee is charged only once the first batch of cars is about to be delivered, so a run whose searches return nothing costs nothing. Also never charged: links that are not Autotrader UK or AutoTrader.ca links (each gets an error row), a car that a second search in the same run finds again, cars past your maxResults, and the summary, info and error rows. The listing page read costs nothing extra.
At these rates, 1,000 cars on the Free plan come to $0.81 plus $0.003. Apify’s free plan includes $5 of credit a month, which the README puts at about 6,000 cars.
Speed
From the README’s test runs on Apify: 30 UK cars with details took 27 to 37 seconds, 144 UK cars with details took 69 seconds, 100 Canadian cars with details took 13 seconds, and 1,000 UK cars from the result cards alone took about a minute. A result page holds 20 cars, and with details on each car is one more page, read 10 at a time.
Honest limits
- 2,000 cars per UK search. Autotrader UK itself shows at most 2,000 cars (100 pages) for one search. The actor allows up to 5,000 per search and 50 searches per run, so split a big search by price band or year.
- No US site. Autotrader.com refuses plain automated requests and is not covered.
- Dealers only for contact data. Private sellers keep their town and nothing else that identifies them.
- Keywords are UK only. The
keywordsfield (words the advert must contain, such as “panoramic roof”) works on Autotrader UK only. - Empty postcode means national. With no UK postcode the search covers the whole UK, and distances count from central London.
- Sold cars. A car sold between the search and the listing page read keeps its card fields and gets
details_error: "not_found".
The same idea, a scheduled search that turns a listings site into a table you can price from, runs through our post on tracking US retail prices and stock too.
Where to start
Run the first JSON above with maxResults at 30 to see the row shape, then widen it. When you need the other markets, the AutoScout24 Scraper, mobile.de Scraper and Carsales.com.au Scraper cover Europe, Germany and Australia.
Explore the scraper referenced in this article: inputs, outputs, and pricing, then run it on Apify.
Frequently asked questions
Does the Autotrader Scraper work on Autotrader.com in the US? +
No. Autotrader.com refuses plain automated requests, so the actor covers Autotrader UK (autotrader.co.uk) and AutoTrader Canada (autotrader.ca) only. For Australia, Germany and the wider European market there are separate actors for Carsales, mobile.de and AutoScout24.
Can I get phone numbers for private sellers? +
No. Dealer rows carry the dealer's name, address, postcode, phone and rating. Private seller rows keep only the town, with no name and no phone number, so lead lists built from this data are dealer lists.
What does a run cost? +
Each car row costs $0.81 per 1,000 on the Apify Free plan and $0.78 per 1,000 on Gold and above, plus a $0.003 start fee per run. The start fee is charged only after a search has returned cars, and the listing page read for each car costs nothing extra.
How do I get more than 2,000 cars for one model? +
Autotrader UK shows at most 2,000 cars for a single search. Split the search into price bands with priceMin and priceMax, or into year ranges with yearMin and yearMax, and run them together. A car that two of those searches find is delivered and charged once.
Build US Attorney and Law Firm Lead Lists by Practice Area and City
Pull US lawyers from the Martindale-Hubbell directory by practice area and city, with firm, phone, website, bar admissions and years licensed, and turn them into a lead list your team can work.
The B2B Lead Generation Stack: Maps Leads, Website Contact Finder, and Email Verification
A three-step pipeline that finds local businesses, fills in missing contacts, and verifies every email before a cold outreach campaign goes out.
Real Estate Agent Lead Lists: Extracting Contact Data from Redfin and Realtor.com
Build agent and brokerage lead lists by scraping Redfin and Realtor.com listings together, deduping agents across both sources for wider coverage.
Food Delivery Restaurant Data: Menus, Prices, Fees and Lead Lists From Uber Eats, Glovo and iFood
Pull restaurants, full menus with prices, delivery fees, ratings and business contact fields from Uber Eats, Glovo and iFood for any address, one row per restaurant.