eBay Vehicle Scraper — Cars & Vans with Full Specs

What does eBay Vehicle Scraper do?

eBay Vehicle Scraper crawls eBay Motors and extracts full structured data from car and van listings — including price, mileage, vehicle specs, seller contact details, photos, and the complete seller description. You filter by model year, mileage range, listing type, and condition, and the Actor paginates automatically, visits each detail page, and saves results to an Apify dataset plus downloadable CSV files.

Because it runs on the Apify platform you also get scheduling, API access, proxy rotation, run history, and integrations with Google Sheets, webhooks, and 1,500+ other tools — without managing any infrastructure.

Why use this scraper?

Manually monitoring eBay Motors for specific vehicles is slow, inconsistent, and easy to miss. This Actor automates the entire process and gives you clean, structured data you can query, sort, and feed into other systems.

Common use cases:

• Fleet buyers tracking late-model ex-rental or company cars with heavy mileage at low prices
• Used car dealers monitoring competitor pricing, trade opportunities, and stock availability
• Market researchers studying depreciation curves, listing turnover, and price trends across model years
• Automotive data teams who need recurring eBay vehicle datasets delivered via API or CSV export
• Lead generation for businesses that want fresh qualifying listings without manually reviewing hundreds of results

How to use it

1. Open the Actor in Apify Console.
2. In the Input tab, select your target model years (default: 2023–2026).
3. Set your minimum and maximum mileage to define the qualifying range.
4. Choose condition, listing type, and sort order to narrow the results.
5. Set Max Search Result Pages to control how many pages to crawl.
6. Keep Apify Residential proxy enabled for reliable results.
7. Click Start. The Actor paginates search results, visits each listing, and saves data.
8. When complete, open the Dataset tab for structured results or download the CSVs from the Key-Value Store.

Schedule the Actor daily or hourly to build a time-series dataset of eBay vehicle listings.

Input

All fields are configured in the Apify Input tab or via JSON.

Field	Type	Default	Description
years	string list	["2023","2024","2025","2026"]	Vehicle model years to include in the eBay search
condition	select	Used	Any Condition / New / Used
statusCategory	select	All	All / Auction / Buy It Now / Best Offer
sortBy	select	Newly Listed	Sort order for search results
maxPages	integer	5	Max search result pages per run (0 = unlimited)

| minMileage | integer | 80000 | Minimum mileage to mark a listing as qualifying (0 = no lower limit) | | maxMileage | integer | 0 | Maximum mileage to mark a listing as qualifying (0 = no upper limit) | | maxConcurrency | integer | 3 | Number of parallel browser pages (1–5) | | proxyConfiguration | proxy | Residential | Proxy settings — residential strongly recommended |

Example JSON input

{
  "years": ["2023", "2024", "2025"],
  "condition": "3",
  "statusCategory": "LH_BIN",
  "sortBy": "10",
  "maxPages": 3,
  "minMileage": 80000,
  "maxMileage": 150000,
  "maxConcurrency": 2,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "GB"
  }
}

Output

Results are stored in the default dataset and in two CSV files in the Key-Value Store.

Dataset example

{
  "id": "358571908536",
  "url": "https://www.ebay.co.uk/itm/358571908536",
  "title": "KIA STONIC 1.0T GDi 48V GT-Line S 5dr DCT",
  "price": "£16,295.00",
  "mileage": "34316",
  "firstSeenAt": "2026-05-19T10:37:06.840Z",
  "qualifies": false,
  "bidInfo": null,
  "condition": "Used",
  "conditionDescription": "An item that has been previously used...",
  "images": [
    "https://i.ebayimg.com/images/g/tXIAAeSwGTpqDDOX/s-l500.webp"
  ],
  "aboutThisItem": {
    "Year": "2023",
    "Mileage": "34316",
    "Body Type": "Estate",
    "Exterior Colour": "Grey",
    "Fuel Type": "Petrol",
    "Transmission": "Automatic",
    "Manufacturer": "Kia",
    "Model": "Stonic",
    "Number of Previous Owners": "1",
    "Service History Available": "Yes"
  },
  "breadcrumb": [
    { "text": "Motors", "url": "https://www.ebay.co.uk/b/bn_7001210476" },
    { "text": "Cars", "url": "https://www.ebay.co.uk/b/bn_1839037" },
    { "text": "Kia Cars", "url": "https://www.ebay.co.uk/b/bn_36936399" }
  ],
  "description": "Here at Lloyd Kia South Lakes we are delighted to present this KIA STONIC...",
  "sellerName": "lloydmotorgroup",
  "sellerUrl": "https://www.ebay.co.uk/sch/lloydmotorgroup/m.html?...",
  "sellerId": "4429486",
  "sellerContact": "0 153 976 6936",
  "sellerJoinedDate": "Joined Dec 2020"
}

CSV files (Key-Value Store)

File	Contents
all-listings.csv	Every listing processed in the run
high-mileage-listings.csv	Only listings where qualifies: true

You can also download the dataset in JSON, HTML, CSV, or Excel directly from the Dataset tab.

Data fields

Field	Format	Description
id	string	eBay item ID
url	string	Direct link to the eBay listing
title	string	Listing title
price	string	Displayed price (e.g. £8,995.00)
mileage	string	Mileage extracted from card or detail page
firstSeenAt	ISO 8601	Timestamp when the listing was first captured
qualifies	boolean	true if mileage is within your min/max range
bidInfo	string / null	Auction bid count and time remaining, if applicable
condition	string	Listing condition (e.g. Used)
conditionDescription	string / null	Full condition description from the popup
images	string[]	All listing photo URLs
aboutThisItem	object	Structured vehicle specs (Make, Model, Year, Fuel, etc.)
breadcrumb	array	Navigation path with text and URL
description	string	Full seller description text from the listing
sellerName	string	Seller's eBay username
sellerUrl	string	Link to the seller's eBay store
sellerId	string	Numeric eBay seller ID
sellerContact	string / null	Seller phone number or contact info
sellerJoinedDate	string / null	Date seller joined eBay (e.g. Joined Dec 2020)

Deduplication

The Actor remembers every listing it has processed using the SEEN_LISTINGS key in the Key-Value Store. On each run it checks whether a listing was already seen within your lookback window. Listings seen within that window are skipped so you do not get duplicate records when you schedule recurring runs.

Cost and performance

This Actor uses Puppeteer (full Chrome browser) with Apify SDK v3 and Crawlee. Browser-based crawling is required because eBay uses JavaScript rendering and anti-bot protections.

Key cost drivers:

• Proxy usage — residential proxies cost more per request but are far more reliable than datacenter IPs
• Number of listings — each detail page opens a full browser tab
• Concurrency — higher values finish faster but use more memory and proxy quota

Tips to keep costs low:

• Run a single-page test (maxPages: 1) before scaling
• Lower maxConcurrency to 1–2 if you see frequent retries or blocks
• Narrow your year range or mileage filters to reduce the number of detail pages visited

Tips

• Set minMileage: 0 and maxMileage: 0 to collect all listings regardless of mileage (full market sweep)
• Set statusCategory: LH_Auction to track live auctions only, including bid info
• Set sortBy: "1" (ending soonest) to prioritise auctions about to close
• The sellerContact field often contains a dealer phone number — useful for lead-generation workflows
• Connect the Actor to Apify webhooks or Google Sheets integration to get alerts when new qualifying listings appear
• Use separate scheduled runs with different years values to keep model-year datasets independent

Disclaimer

Ensure your use of this Actor complies with eBay's Terms of Service, applicable data protection laws (GDPR), and your organisation's data policies. You are responsible for how collected data is stored and used.

This Actor is intended for listing analysis and market research only. Do not use it to collect, expose, or misuse personal or sensitive data about private sellers.

For bugs, feature requests, or questions please use the Issues tab on the Actor's source repository.