EasyAuto123 Cars Scraper

Extract EasyAuto123 used vehicle listings into a clean dataset for pricing analysis, stock tracking, lead routing, and vehicle comparison workflows.

What You Get

Each saved vehicle can include:

• Listing ID, EasyAuto123 URL, title, make, model, variant, release year, VIN
• Displayed price, price type, odometer, fuel, transmission, drive type, engine capacity, colour, body/type labels
• Store location, region, state, store name, public phone, public email, address, and rating when available
• Primary image, full image list, car category, banner, stock status, update timestamp
• Price component rows, full store object, and full source vehicle object for advanced exports

Input Modes

Search Filters

Use mode: search to build a vehicle search from filters. Supported filters include:

• Keywords, makes, models, variants
• Dealer locations
• Vehicle types, fuel types, transmissions, colours
• Lifestyle labels, vehicle sizes, EasyAuto123 car types
• Year, price, and odometer ranges
• Sort order

URLs

Use mode: url for one or more EasyAuto123 URLs. Supported examples:

• https://easyauto123.com.au/buy/used-cars?page=1&limit=20
• https://easyauto123.com.au/buy/used-cars?page=2&limit=20&fuel-type=Hybrid
• https://easyauto123.com.au/buy/used-cars/details/2014/TOYOTA/CAMRY/Hybrid-HL/SA/Adelaide/Mile-End-South/Automatic/White/Sedan-Hybrid/6T1BD3FK40X141250

Limits

maxItems is the main cap. The actor stops once that many vehicles have been saved or no more matching vehicles are available.

maxPages is optional. Leave it as 0 to avoid a page cap. Set it only when you want to limit how far a search can go.

Detail Fields

Keep fetchDetails enabled when you want the richest vehicle records. Turn it off for faster list-level runs when you only need listing data.

Resume & Recurring Updates

Two distinct tools, both optional:

• resumeFromRunId continues ONE specific interrupted run. Paste a previous run ID or dataset ID and this run will skip vehicles it already saved there, instead of re-scraping (and re-billing) them.
• incrementalMode is for scheduling the SAME search again and again (daily, hourly, ...) and only getting what changed. Turn it on and the actor remembers the previous run of this exact search itself — no run/dataset id needed. The first run returns every matching vehicle as NEW. Later runs return only NEW, UPDATED, and REAPPEARED vehicles by default.
  • Each output row gains changeType (NEW / UPDATED / UNCHANGED / REAPPEARED / EXPIRED), changedFields, firstSeenAt, and lastSeenAt.
  • emitUnchanged (off by default) also returns vehicles with no change, marked UNCHANGED — this returns and bills extra rows.
  • emitExpired (off by default) also returns vehicles that were tracked before but are no longer found, marked EXPIRED. This only happens once a run has scanned the full tracked search — a run capped by maxItems, or one using resumeFromRunId, skips expiry detection for that run rather than risk marking a live vehicle as gone.
  • State is tracked separately per distinct combination of filters (mode, keywords, makes, models, variants, locations, vehicle type, fuel type, transmission, colour, lifestyle, vehicle size, car type, year/price/odometer range, sort, and whether detail fields are fetched). maxItems, maxPages, and delivery-only settings (proxy, MCP connectors, notifications) never affect which state a run uses — raising the item cap tomorrow does not start a new baseline.
  • stateKey optionally names the monitoring campaign, letting you deliberately share state across otherwise different filter setups (or just keep a stable, memorable key). Leave it empty to let the actor derive one automatically from the filters above.
  • A field-level change is only reported when the underlying value genuinely changes between two successfully-observed values. A vehicle's own last-updated timestamp, and its (rotating, signed) image links, do not by themselves count as a change — see Notes below.
  • incrementalMode and resumeFromRunId can be combined only to bootstrap a brand-new monitoring campaign from an existing pull (no incremental state saved yet for that state key); once state exists, remove resumeFromRunId or pick a different stateKey.

Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape, and the Apify dataset is never changed.

What gets written to the connector: a condensed, human-readable summary of each record (not the full JSON). Each item becomes one entry with a title (the vehicle name) and its key fields flattened to plain text. Nested objects are collapsed to their main value and long lists are trimmed. The complete record always stays in the Apify dataset.

1. Authorize a connector once under Apify → Settings → Integrations (Notion, Linear, Airtable, or Apify).
2. Select it in the "Pipe results into your apps" input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For Notion, also set notionParentPageUrl to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

Proxy

The actor uses Apify Proxy by default. Keep the prefilled proxy configuration for normal runs, or provide your own proxy settings if your workflow requires it.

Example Input

{
  "mode": "search",
  "makes": ["Toyota"],
  "models": ["CAMRY"],
  "fuelTypes": ["Hybrid"],
  "maxItems": 20,
  "maxPages": 0,
  "fetchDetails": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "mcpConnectors": []
}

Output Example

{
  "listingId": "f5504a4d-5263-4cc0-fc0a-08debf9c24ec",
  "url": "https://easyauto123.com.au/buy/used-cars/details/2011/SUBARU/IMPREZA/2.0i-L/QLD/Brisbane/Hendra/Automatic/White/Sedan/JF1GJ7KC5CG003176",
  "title": "2011 Subaru Impreza 2.0i-L",
  "make": "SUBARU",
  "model": "IMPREZA",
  "variant": "2.0i-L",
  "year": 2011,
  "price": 10990,
  "odometer": 168196,
  "vin": "JF1GJ7KC5CG003176",
  "fuelType": "Petrol",
  "transmission": "Automatic",
  "location": "Hendra",
  "state": "QLD",
  "storeName": "easyauto123 Hendra"
}

Notes

The dataset can include additional fields beyond the table view. Export JSON if you need nested store details, price components, image metadata, or the full vehicle object.

Two fields are excluded from incremental mode's change detection but are still returned on every row: the vehicle's updatedAt timestamp (the site's own last-modified stamp; genuine content changes are already caught by diffing price, status, odometer, and the other fields directly), and the query parameters on image links (imageUrls, primaryImage, and the orbit/sphere image lists), which are per-fetch signed download tokens that change on every page load even for the exact same photo.