AutoTrader UK Vehicle Listings Scraper

Export public UK vehicle listings, prices, specifications, dealer details and finance terms from AutoTrader search or detail URLs. Try the input examples to begin.

Data fields

FieldTypeDescription
advertIdstringValue exported as advertId.
sourceUrlstringValue exported as sourceUrl.
sourceSearchUrlstringValue exported as sourceSearchUrl.
pageintegerValue exported as page.
titlestringValue exported as title.
makestringValue exported as make.
modelstringValue exported as model.
variantstringValue exported as variant.

Input preview

startUrlsAutoTrader search or vehicle URLs *
maxItemsMaximum vehicle listings
includeListingDetailsInclude listing details

API and agents

This actor can be run through Apify API, datasets, webhooks, schedules, and the official Apify MCP server.

Ready-to-run examples

Open a saved Apify example, adjust the input, and run the actor in your own Apify account.

View all examples

How this actor works

See example inputs, outputs, API usage, and practical limits before running this actor on Apify.

Open Apify page

This AutoTrader scraper exports public UK vehicle listings from AutoTrader search pages and individual vehicle pages. Build a structured vehicle catalogue for comparison, dealer-inventory research, and saved-search monitoring.

Quick start

  1. Paste a public AutoTrader UK car-search URL containing a postcode into startUrls.
  2. Start with maxItems: 10. Keep includeListingDetails: true for fuller records.
  3. Run the Actor and download the dataset as JSON, CSV or Excel, or retrieve it through the API.
{
  "startUrls": [{ "url": "https://www.autotrader.co.uk/car-search?postcode=SW1A%201AA&make=BMW" }],
  "maxItems": 10,
  "includeListingDetails": true
}

Use a public /car-details/{advertId} URL instead when you already know the vehicle. Only UK car searches and car-detail pages are supported. This is not the US AutoTrader website.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

https://youtu.be/1OW8gOqlZbY?t=25

What you get

Each dataset row is one public vehicle listing. The Actor preserves the requested source URL and collects the listing fields that AutoTrader makes publicly visible.

Field group Included data
Identity advertId, sourceUrl, sourceSearchUrl, title, make, model, variant, year, registration
Vehicle specification mileage, fuelType, transmission, bodyType, specifications, features
Price and finance price, finance including public representative finance details when shown
Seller dealer including public name, contact, rating and location fields when shown
Media and checks images, history, vehicleCheck when shown on the public listing
Collection context page, scrapedAt

Optional sections can be omitted, empty or null when the public page does not show them. The Actor does not invent unavailable vehicle, dealer, finance, or check data.

A minimal illustrative row is shown below (shape only, not a live advert):

{
  "advertId": "123456789012345",
  "sourceUrl": "https://www.autotrader.co.uk/car-details/123456789012345",
  "title": "Example vehicle",
  "scrapedAt": "2026-10-25T00:00:00.000Z"
}

Nested sections retain the source's structure. In particular, price is not guaranteed to be a number, and mileage can be a formatted string or specification array. Inspect JSON before flattening these fields into a spreadsheet.

Who is it for?

  • Vehicle buyers comparing advertised specifications, mileage, price and finance terms.
  • Dealers and analysts tracking public competitor stock and advertised inventory changes.
  • Researchers building a repeatable UK vehicle dataset from saved AutoTrader searches.
  • Data teams and AI users reviewing public vehicle exports in their own analysis workflow.

How you can use the data

  • Prepare a UK vehicle comparison sheet. Copy a public AutoTrader car-search URL including its postcode and collect a small sample. Keep advertId, sourceUrl, sourceSearchUrl and available vehicle details with each observation.
  • Inspect price and mileage before flattening data. Review the JSON for price, mileage and finance, because these can retain nested source structures or formatted text. Compare advertised terms rather than assuming a normalized cash price or finance quote.
  • Review one known advert in more detail. Supply its public car-detail URL for the fuller available record. Direct detail URLs fetch the detail page even when optional search-detail enrichment is off, and source-dependent panels may still be missing.
  • Compare separate inventory exports. Join your own datasets by advertId or source URL, retaining scrapedAt. Any change report is a separate analysis step, and missing or unavailable adverts are not proof of a sale.

Input settings

Input Description
AutoTrader search or vehicle URLs — startUrls Required, nonempty list of public UK car-search or car-detail URLs. Search URLs need a postcode. See the field help for supported URL filters.
Maximum vehicle listings — maxItems Total output cap across all supplied URLs. Default 10, maximum 10,000.
Include listing details — includeListingDetails Defaults to true. Set false for search-card exports. Direct car-detail URLs always fetch the detail page.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

advertId and sourceUrl are the stable identifiers to retain when deduplicating later exports. sourceSearchUrl and page identify where a search result came from. price is the advertised value shown on the page, while finance is a nested object containing only the public finance terms displayed for that listing.

dealer, images, history, and vehicleCheck are nested public sections. Their properties vary by listing, seller type, and whether the page exposes the relevant panel. A vehicle detail URL is the best choice when you need the fullest record for a known advert.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Tips for best results

  • Copy a public UK car-search URL with its postcode. Check the input-field help because not every website filter is supported.
  • Start with 5–10 listings. Review the returned fields before increasing the cap for a new search.
  • Use a direct detail URL for a known advert. It can provide a fuller available record, without guaranteeing every optional section.
  • Keep detail enrichment on when its fields matter. Dealer, finance, media and vehicle-check information depend on available detail-page content.
  • Keep advert identity and original JSON for comparisons. Preserve advertId and sourceUrl, and inspect nested price or mileage fields before importing them into a spreadsheet.

Limits and caveats

This Actor works with anonymous public AutoTrader UK pages only. Sign-in-only, private, removed, expired, or temporarily unavailable listings are not collected. Unavailable detail pages returning HTTP 404 or 410 are skipped with a truthful run-summary reason. Unexpected detail extraction failures preserve collected rows but fail the run rather than reporting a successful empty export. A failed search request can fail the run. Already saved rows remain available. Public page layouts and available fields can differ by advert. Search-card exports omit fields that require a detail-page visit.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~autotrader-uk-vehicles-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "startUrls": [
    {
      "url": "https://www.autotrader.co.uk/car-search?postcode=SW1A%201AA&make=BMW"
    }
  ],
  "maxItems": 10,
  "includeListingDetails": true
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/autotrader-uk-vehicles-scraper').call({
  "startUrls": [
    {
      "url": "https://www.autotrader.co.uk/car-search?postcode=SW1A%201AA&make=BMW"
    }
  ],
  "maxItems": 10,
  "includeListingDetails": true
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/autotrader-uk-vehicles-scraper').call(run_input={'startUrls': [{'url': 'https://www.autotrader.co.uk/car-search?postcode=SW1A%201AA&make=BMW'}], 'maxItems': 10, 'includeListingDetails': True})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with AutoTrader UK Vehicle Listings Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's AutoTrader UK Vehicle Listings Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/autotrader-uk-vehicles-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use AutoTrader UK Vehicle Listings Scraper by Fetch Cat, or give it the identifier fetch_cat/autotrader-uk-vehicles-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

  • “Use Fetch Cat’s AutoTrader UK Vehicle Listings Scraper to collect up to 5 listings from this public UK car-search URL, including its postcode. Show advert IDs, source links and available price and mileage values without assuming they are flat numbers.”
  • “Retrieve one known vehicle from this public AutoTrader UK car-detail URL. Show the fuller available specifications, dealer and public finance information, clearly marking missing sections.”
  • “Collect at most 5 vehicles from my public UK search URL without optional listing-detail enrichment. Keep advert IDs and collection time so I can compare the search-card export with my earlier dataset.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

Support and feedback

For custom additions or integrations, email [email protected].

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥

Common questions

Questions and answers reused from the canonical actor README.

What data can I export with autotrader scraper?

Each row can include public identity, price, mileage, specification, dealer, finance, image, history and vehicle-check fields that the requested listing exposes.

Can I run AutoTrader UK Vehicle Listings Scraper through an API, schedule, or MCP client?

Yes. Use the API examples above, schedule the Actor in Apify, or call it with the MCP tool URL.

How much does it cost to use AutoTrader UK Vehicle Listings Scraper?

Each run has a one-time start event and each successfully produced row has an item event. See the live Pricing tab for current tier rates.

Why does a search URL need a postcode?

AutoTrader's UK public search uses a postcode to return geographically relevant listings.

Can I export one car?

Yes. Provide its public /car-details/{advertId} URL in startUrls.