EasyAuto123 Scraper

EasyAuto123 Scraper at a glance

EasyAuto123 Scraper is a ready-to-run Apify actor from abotapi for collecting lead generation data. Its documented output includes title, price, year, odometer and make, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $2.50 per 1,000 results on the Apify Free plan and from $1.00 on paid plans, with smaller per-run or optional feature charges listed on Apify.

Runs on: Apify cloud: console, API, schedules and integrations
Data type: Lead Generation, Travel, Ecommerce
Pricing: $2.50 per 1,000 results (Free plan), from $1.00 on paid plans
Output: Documented below · JSON, CSV, Excel
Inputs: 33 options

Scrape EasyAuto123 vehicle listings into clean structured data. Extract prices, VINs, odometer readings, make, model, year, trim, specs, images, dealer names, locations, contact details, listing URLs, and optional extra fields for market research, lead generation, and inventory tracking.

What EasyAuto123 Scraper can do

Two ways to build a pull. Search by make, model, variant, dealer location, price, year and odometer range, body type, fuel, transmission, colour, lifestyle, size and EasyAuto123 category, or paste search and vehicle URLs directly.
Listing and detail depth. Turn on detail fields to add engine and drive specifications, ANCAP and CO2 ratings, warranty terms and extra photo sets, fetched from each vehicle's own page.
Dealer details attached. Store name, address, phone, email and rating are attached from EasyAuto123's store directory whenever it is available, no separate lookup needed.
Built for monitoring. Incremental mode tracks the same search across scheduled runs and classifies every vehicle as new, updated, unchanged, reappeared or expired. Read the limits under "Resume and recurring updates" before relying on expiry detection.
Skip what you already have. Point a run at a previous run or dataset and it never re-saves or re-bills vehicles already saved there (see the limit on how far a resumed search walks, below).
Cost control built in. Max items and max pages cap a run before it starts, and detail fields carry a separate, clearly billed surcharge only when they are actually fetched successfully.

Choose what to collect

These inputs let you configure EasyAuto123 Scraper - Vehicle Listings, VINs & Dealer Data. Open the actor on Apify to enter your values and review the current options.

Supported input fields
Input	What it controls
`mode`string · required	Choose whether to build a listing search from filters or start from one or more EasyAuto123 URLs. Choices: search, url
`urls`array	Use this in URLs mode. Add listing search URLs, individual vehicle URLs or the electric and hybrid category page (/buy/electric-and-hybrid-cars, which lists used Hybrid and Electric vehicles). www and http links are normalised to https://easyauto123.com.au. Other category or marketing pages are skipped with a warning. The pre-filled list shows one example of every supported shape (including www and http forms, which are normalised); the shipped default omits the bare listing and page-2 examples because they resolve to the same pages as the first listing URL. An explicit empty list scrapes the first listing page.
`keywords`array	Optional make text, such as Toyota or Ford. A model word on its own matches nothing on the source, so prefer the structured Makes, Models and Variants fields.
`makes`array	Vehicle makes, for example Toyota, Mazda, Ford, BYD, Kia, Hyundai, Mitsubishi, Subaru, Volkswagen, Nissan, Audi.
`models`array	Vehicle models to include, used together with Makes (a model without a matching make is ignored). Use values as shown on EasyAuto123, for example CAMRY, RANGER, HILUX, I30, CX-5.
`variants`array	Optional vehicle variant names, used together with Makes and Models (a variant without a matching make and model is ignored).
`locations`array	Dealer locations in Suburb, STATE form, for example Hendra, QLD or Brooklyn, VIC. The comma matters: the source does not match a plain space.

Show 26 more inputs

More input fields
Input	What it controls
`vehicleTypes`array	Body and type labels, for example SUV, Wagon, Hatchback, Sedan, UTE, 7+ Seater, Hybrid, Electric.
`fuelTypes`array	Fuel labels to include.
`transmissions`array	Transmission labels to include.
`colours`array	Vehicle colours, such as White, Grey, Blue, Black, Silver, Red.
`lifestyles`array	Lifestyle labels, such as Family, City, Tradie, Outdoor Adventure, Eco Friendly.
`vehicleSizes`array	Size labels to include.
`carTypes`array	EasyAuto123 vehicle category, for example "Quality Verified".
`minYear`integer	Only include vehicles from this release year or newer.
`maxYear`integer	Only include vehicles from this release year or older.
`minPrice`integer	Only include vehicles at or above this displayed price.
`maxPrice`integer	Only include vehicles at or below this displayed price.
`minOdometer`integer	Retired: the live source offers no minimum-odometer facet, so this value is ignored. Saved tasks keep working.
`maxOdometer`integer	Only include vehicles at or below this odometer reading.
`sort`string	Result ordering. Choices: price-reduced, price-asc, price-desc, kilometres-asc, kilometres-desc, year-desc, year-asc
`fetchDetails`boolean	Adds fields that are only available on individual vehicle pages. Each successfully enriched item is billed one extra detail-enrichment event on top of the per-item dataset charge; suppressed/unchanged rows are never charged for it. Turn off for cheaper, faster list-level runs when you only need listing data.
`maxItems`integer	Maximum number of dataset items to save. The run stops when this cap is reached or no more matching vehicles are available.
`maxPages`integer	Optional page cap. Leave as 0 for no page cap; max items remains the main limit.
`resumeFromRunId`string	Paste a previous run ID or dataset ID to continue a large crawl of vehicle listings without returning or charging for vehicles already collected there. Use this after an interrupted run, or when continuing a listing pull in another run. For recurring daily monitoring of the same search, use Incremental mode below instead.
`incrementalMode`boolean	Turn this on for daily or recurring monitoring. The first run returns all matching vehicles as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED vehicles. A vehicle counts as UPDATED when any returned field changes, except updatedAt, the raw source payloads, the changing signature part of image links, image order, and anything you list under Ignore fields below. Turn on "Emit unchanged" or "Emit expired" only when you also want those vehicles returned (and billed). State is kept separately for each filter combination and detail-mode setup; use State key when you want to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.
`stateKey`string	Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from the filters and detail setting - different searches then never mix state with each other.
`emitUnchanged`boolean	Off by default. Turn on to also return vehicles that have not changed since the last run, marked UNCHANGED. This returns - and bills - extra rows you already have, so leave it off unless you specifically want the full snapshot every run.
`emitExpired`boolean	Off by default. Turn on to also return vehicles that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search - not when Max items capped it or when Resume was used. This returns - and bills - extra synthetic rows, so leave it off unless you need expiry tracking.
`ignoreFieldsForChanges`array	Field names that must not make a vehicle count as UPDATED. Use a top-level name such as banner, or a dotted path for nested data such as engineSpecifications.power. The fields are still returned in the output - they are only left out of change detection and changedFields. Always ignored already: updatedAt, rawVehicle, storeRaw, detailFetched, and the changing signature part of image links.
`mcpConnectors`array	Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify → Settings → Integrations, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON. The complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).
`notionParentPageUrl`string	URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.
`maxNotifyListings`integer	Cap on items written to each connector per run. Does not affect the dataset.

Fields in the output

The documented dataset includes the fields below. Availability can depend on the source page and selected mode.

titleTitle

pricePrice

yearYear

odometerOdometer

makeMake

modelModel

vinVIN

fuelConsumptionFuel L/100km

ancapRatingANCAP

co2EmissionCO2 g/km

locationLocation

stateState

Show 31 more fields

storeNameStore

urlURL (link)

changeTypeChange type (incremental mode) (text)

changedFieldsChanged fields (incremental mode) (array)

firstSeenAtFirst seen (incremental mode) (date)

lastSeenAtLast seen (incremental mode) (date)

listingIdID

storeAddressStore address

storePhoneStore phone

storeEmailStore email

storeRatingStore rating

primaryImagePrimary image (image)

imageCountPhotos

imageUrlsImage URLs (array)

variantvariant

priceTypepriceType

driveawayPricedriveawayPrice

fuelTypefuelType

transmissiontransmission

driveTypedriveType

engineCapacityengineCapacity

cylinderscylinders

seatsseats

torquetorque

colourcolour

stockNumberstockNumber

warrantywarranty (object)

engineSpecificationsengineSpecifications (object)

driveSpecificationsdriveSpecifications (object)

suspensionsuspension (object)

detailFetcheddetailFetched

Example output

An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.

{
  "listingId": "sample-listing-00001",
  "url": "https://easyauto123.com.au/buy/used-cars/details/2019/TOYOTA/COROLLA/Ascent-Sport/QLD/Sample-Region/Sample-Suburb/Automatic/White/Hatchback/SAMPLEVIN00000001",
  "title": "2019 Toyota Corolla Ascent Sport",
  "make": "TOYOTA",
  "model": "COROLLA",
  "variant": "Ascent Sport",
  "year": 2019,
  "price": 24990,
  "priceType": "Drive Away",
  "odometer": 52000,
  "vin": "SAMPLEVIN00000001",
  "fuelType": "Petrol",
  "transmission": "Automatic",
  "driveType": "FWD",
  "engineCapacity": "1800",
  "colour": "White",
  "vehicleTypes": [
    "Hatchback"
  ],
  "state": "QLD",
  "location": "Sample Suburb",
  "region": "Sample Region",
  "carType": "Quality Verified",
  "status": "IN-STOCK",
  "primaryImage": "https://example.com/sample-vehicle-1.jpg",
  "imageCount": 12,
  "storeName": "easyauto123 Sample Suburb",
  "storeAddress": "1 Sample Street, Sample Suburb QLD 4000",
  "storePhone": "(07) 5550 1234",
  "storeEmail": "sales@example.com",
  "storeRating": 4.6
}

Ways to use this data

Dealers and resellers: monitor EasyAuto123 stock, pricing and store coverage against your own inventory.
Price and market researchers: track how price, odometer and stock status move for specific makes, models or price bands over time.
Lead generation and CRM teams: pull dealer contact details and vehicle specs to route enquiries to the right store.
Comparison sites and marketplaces: build a feed of listings with specs, images and store details for your own site or app.
Finance, insurance and valuation teams: gather year, odometer, VIN and specification data to support valuations.

Before you run

Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.

Questions about this actor

What data does EasyAuto123 Scraper return?

The documented output for EasyAuto123 Scraper includes title, price, year, odometer, make, model, vin and fuel l/100km. Availability of each field depends on the source page and the selected mode.

How much does EasyAuto123 Scraper cost?

It costs $2.50 per 1,000 results on the Apify Free plan and from $1.00 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.

Can I get only new or changed vehicles on a schedule?

Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new, updated and reappeared vehicles by default, and unchanged ones are not billed unless you turn on Emit unchanged.

What's the difference between Resume and Incremental mode?

resumeFromRunId continues ONE specific interrupted run from a pasted run or dataset ID. Incremental mode is for running the SAME search again and again on a schedule and remembers its own state, no ID needed. Use Resume after a run stops partway through; use Incremental mode for ongoing monitoring. Both reuse the page-walk rules in "Resume and recurring updates" above: a resumed search walks past the pages already saved (listings only) instead of stopping, and an incremental run stops at the site's own last page or when Max items is reached.

Does a run with several pasted URLs read all of them in full?

Yes. Each URL is paged from its start to the site's own last page, or until Max pages or Max items stops the run. Vehicles already collected from an earlier URL in the same run are skipped (never saved or billed twice), but their listing pages are still read, so overlapping URLs take a little longer.

Why did my run fail instead of returning an empty dataset?

If a listing page still cannot be fetched after several retries, the run is marked failed instead of succeeded (anything already saved before that page stays in the dataset), so a blocked or unreachable site is not mistaken for "no matching vehicles". Run it again in a few minutes. Two softer failures do not stop the run: a vehicle whose detail page cannot be read still ships with its listing-level fields (and no detail surcharge), and if the store directory cannot be read, vehicles ship without the dealer name, address, phone, email and rating.