US Autotrader Scraper avatar

US Autotrader Scraper

Pricing

from $2.50 / 1,000 results

Go to Apify Store
US Autotrader Scraper

US Autotrader Scraper

Scrape Autotrader.com vehicle listings nationwide or for a specific US state.

Pricing

from $2.50 / 1,000 results

Rating

0.0

(0)

Developer

Fahim Mahmud Chisti

Fahim Mahmud Chisti

Maintained by Community

Actor stats

0

Bookmarked

57

Total users

19

Monthly active users

3 days ago

Last modified

Features

Limited permissions

Share

What does US Autotrader Scraper do?

US Autotrader Scraper extracts public vehicle listings from Autotrader.com into a structured Apify dataset. It supports nationwide searches, verified state-specific results, keyword searches, filtered Autotrader URLs, and direct vehicle-detail URLs. Instead of rendering the site in a browser, the Actor reads the same search JSON API the Autotrader page itself calls, through a built-in web unblocker, so you need no proxy of your own. One request returns up to 100 listings, so runs are fast and cheap.

Why use US Autotrader Scraper?

  • Monitor vehicle inventory across the entire United States.
  • Restrict saved vehicles to any US state or Washington, DC.
  • Compare prices, mileage, model years, trims, and sellers.
  • Track newly listed vehicles using newest-first search and optional age filtering.
  • Export results through the Apify API or as JSON, CSV, Excel, XML, RSS, or HTML.

How to scrape Autotrader vehicles

  1. Open the Actor's Input tab.
  2. Add search keywords, Autotrader search URLs, or direct vehicle URLs.
  3. Select Entire United States or Specific state.
  4. When using a specific state, select its two-letter state code.
  5. Set item/page limits and start the Actor.

The Actor adds location parameters to search URLs but also verifies each listing's location before saving state-specific output. This prevents nearby out-of-state inventory from leaking into state results.

Input

  • searchKeywords — phrases such as Toyota Camry, Ford F-150, or electric SUV.
  • startUrls — Autotrader search or vehicle-detail URLs. Existing filters (including zip, radius, and sort) are preserved.
  • locationScope — nationwide or state.
  • state — required for state scope; supports all 50 states and DC.
  • maxItems — maximum listings saved across all searches; 0 means unlimited.
  • maxPagesPerSearch — maximum result pages per search.
  • maxListingAgeDays — optional publication-age limit. Listings without a known date are excluded.
  • scrapeItemDetails — also loads each vehicle (private-seller listings through the Marketplace JSON API, others through the vehicle page). Only works with your own proxies: through the built-in unblocker Autotrader refuses vehicle pages, so listings are saved from the search API data, which already carries VIN, mileage, price, description, specifications, seller and photos.
  • saveDebugResponses — store raw API/page responses in the key-value store (DEBUG_PAGE_*) when diagnosing missing fields (default false).
  • duplicateCheck — skip detail scraping for listing URLs already known (default false).
  • duplicateCheckApiUrl — optional POST exists API; leave empty for Apify storage only.
  • duplicateCheckStoreName — named KV store (default vehicle-listing-urls).
  • proxyConfiguration — leave on No proxy (default): the Actor uses its own web unblocker, billed per answered search request (see "Cost and performance"). Autotrader refuses Apify Proxy IPs, so an Apify Proxy setting is replaced by the built-in unblocker. Your own proxy URLs are used as given; see "Using your own proxies" below.

Nationwide example:

{
"searchKeywords": ["Toyota Camry"],
"locationScope": "nationwide",
"maxItems": 100,
"maxPagesPerSearch": 3,
"scrapeItemDetails": true
}

Texas example:

{
"startUrls": [
{
"url": "https://www.autotrader.com/cars-for-sale/all-cars?startYear=2020&endYear=2026"
}
],
"locationScope": "state",
"state": "TX",
"maxItems": 50,
"scrapeItemDetails": true
}

Skip existing listings (duplicate check)

With detail scraping on, every vehicle costs one extra request on the residential session. On scheduled re-runs, most results are often listings you already stored. Duplicate check skips those URLs so you do not pay again for vehicles you already have.

Enable it with duplicateCheck: true (default false).

If N consecutive listing URLs in a search are known duplicates (N = duplicateCheckLeadingStop, default 20), that search stops (no further pages) to avoid paying for known inventory.

Modes

  • When duplicateCheckApiUrl is set, the Actor POSTs batches of up to 500 listing URLs to your endpoint, then skips URLs returned in existing. It also reads and updates the named Apify Key-Value store. A URL is skipped if either your API or the store marks it as known.
  • When duplicateCheckApiUrl is empty, the Actor uses the Apify Key-Value store only (no external API).

API contract

// Request
{ "listingUrls": ["https://example.com/listing/1", "https://example.com/listing/2"] }
// Response
{
"existing": ["https://example.com/listing/1"],
"missing": ["https://example.com/listing/2"]
}

listingUrls may also be a single string. URLs are normalized (query string and trailing slash ignored). No auth header is required for public endpoints. If the API call fails or exceeds a 20s timeout, the Actor fail-opens and scrapes the batch.

After a listing is saved successfully, its URL is written to the named store under the KNOWN_LISTING_URLS record so future runs skip it even without an API. Cached URLs expire after 30 days, and the store is capped at 50,000 entries (oldest first). Legacy boolean true entries are migrated to timestamps on load.

Example:

{
"searchKeywords": ["Toyota Camry"],
"locationScope": "nationwide",
"maxItems": 100,
"duplicateCheck": true,
"duplicateCheckApiUrl": "https://your-api.example.com/listings/exists",
"duplicateCheckStoreName": "vehicle-listing-urls"
}

Output

The output uses the same vehicle contract as the eBay and Craigslist Actors:

{
"itemId": "765432109",
"title": "2022 Toyota Camry XSE",
"listedAt": "2026-07-18T14:30:00.000Z",
"price": "29995",
"currency": "USD",
"year": "2022",
"make": "Toyota",
"model": "Camry",
"trim": "XSE",
"mileage": "31220",
"vin": "4T1TESTVIN1234567",
"location": "Austin, TX",
"seller": "Example Toyota",
"imageUrl": "https://images.autotrader.com/example.jpg",
"images": ["https://images.autotrader.com/example.jpg"],
"url": "https://www.autotrader.com/cars-for-sale/vehicle/765432109"
}

When the Actor is started from an Apify Task, each dataset item also includes taskId and taskName so you can track which Task produced it. Direct Actor runs set both to null.

Additional fields include description, condition, body type, engine, transmission, drivetrain, fuel type, colors, forSaleBy (Private Seller or Dealer), title status, source URL, page number, scrape timestamp, and a specifics object. specifics carries what the search API adds per listing: dealIndicator, kbbFairPurchasePrice, msrp, priceReduced, distance (miles from the search zip), mpg, doors, stockNumber, daysOnSite, sellerRating, sellerReviewCount, sellerPhone, state. Fields unavailable on a listing remain null.

Autotrader usually does not publish an exact listing timestamp. When a "days on site" / "days on market" counter is available, the Actor prefers that over embedded inventory dates and derives listedAt from the US Eastern calendar day (noon UTC, so the civil date stays stable across US timezones). It marks this with "listedAtDerivedFrom": "daysOnSite" in specifics. Private-seller listings sometimes expose no counter at all; if Autotrader flags them as newly listed, the Actor sets listedAt to today and marks it with "listedAtDerivedFrom": "isNewlyListed". The maxListingAgeDays filter uses the same value. Mileage strings like 32K mi are expanded to full mile counts.

Cost and performance

The Actor is HTTP-only: no browser, 256-512 MB of memory is plenty, and one search request returns up to 100 listings in a few seconds. A 100-listing run finishes in about a minute for a fraction of a compute unit, and you pay no proxy traffic.

Pricing is pay per event: each saved vehicle is one result, and each search request answered through the built-in web unblocker is one search request (up to 100 listings). Refused requests that are retried are not charged, and runs with your own proxy URLs pay no search-request events. With duplicateCheck on, a search page whose listings you already have still costs one search request but no results. The run stops by itself when it reaches the maximum cost per run you set.

Autotrader's edge protection (Akamai) still turns away some requests that go through the unblocker, so a refused search page is retried up to thirty times before the run gives up. If every attempt stays blocked and nothing is scraped, the run ends as FAILED instead of succeeding with an empty dataset, and the status message carries the last error. Use maxItems, maxPagesPerSearch, and maxListingAgeDays to control cost, enable duplicateCheck on scheduled re-runs to skip known vehicles, and leave scrapeItemDetails off when the search fields are enough. State searches may inspect extra listings because location is verified before output.

Tips

  • Use US residential proxies, either the default Apify pool or your own provider; datacenter IPs are blocked on sight.
  • Use filtered Autotrader search URLs for make, model, price, year, mileage, body style, and condition filters. The Actor translates the URL path (used-cars, by-owner, make, model, city-st) and query string into API parameters; make codes use Autotrader's own table, model codes are a best-effort upper-casing of the slug.
  • Paste the URL of an Autotrader search with a zip= parameter for local searches; without one, a city page (.../austin-tx) is searched from its state's capital zip code.
  • Enable duplicateCheck on scheduled re-runs to skip vehicles you already stored.
  • The run Container URL exposes / and /status for live progress while the Actor is active.

Using your own proxies

The built-in web unblocker is the default and needs no setup. If you would rather use your own residential or unblocker provider, no code change is needed:

  1. In the Input tab, open Proxy configuration, switch to Your own proxies, and paste one URL per line in the form http://user:pass@host:port. In JSON this is "proxyConfiguration": { "useApifyProxy": false, "proxyUrls": ["http://user:pass@host:port"] }.
  2. The Actor uses one URL for its session and moves to the next URL after a block. Prefer sticky-session URLs: most providers pin the exit IP to a session id written into the username or password. Write {session} where that id goes, for example http://user-session-{session}:pass@host:port, and the Actor puts its own session id there, so the IP stays the same for the whole run and a new one is picked only after a block. Without the placeholder, list several URLs with different session ids yourself. A plain rotating gateway changes the IP on every request and gets re-blocked.
  3. The proxy must allow HTTPS CONNECT. A proxy that is down fails fast with a proxy connection error in the log rather than an Akamai block page.
  4. An IPRoyal Web Unblocker URL (unblocker.iproyal.com) is detected and used with a plain HTTP/1.1 client, as IPRoyal documents. Do not add _country-us: the unblocker answers HTTP 422 to it.

Scrape only public information and comply with applicable law, Autotrader's terms, and reasonable request rates. The Actor does not intentionally collect private contact information. Autotrader can change its application or blocking behavior; if a run fails, provide its run ID and affected URL through the Actor's Issues tab.