AutoTrader Vehicle Search avatar

AutoTrader Vehicle Search

Pricing

from $4.13 / 1,000 results

Go to Apify Store
AutoTrader Vehicle Search

AutoTrader Vehicle Search

Search public Autotrader US vehicle inventory by keyword and optional ZIP radius. Export normalized listing titles, prices, source links, and other available vehicle fields.

Pricing

from $4.13 / 1,000 results

Rating

0.0

(0)

Developer

AgentX

AgentX

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 days ago

Last modified

Share

AutoTrader Vehicle Search is a autotrader scraper that searches public Autotrader United States inventory by vehicle phrase and optional location and returns normalized, source-linked rows with 37 documented fields. The edition keeps the required United States market input while fixing the source route to Autotrader, so user intent remains explicit without a platform selector.

Apify Users Apify Runs Price Capability API + MCP ready

  • Autotrader-only route: The Actor exposes no platform selector and attributes qualifying records to the named source.
  • Required market input: country remains required and the focused runtime accepts United States; fixed routing does not justify deleting it.
  • Optional ZIP context: A resolvable US city or ZIP applies the source-native 50-mile search radius.
  • 37-field contract: The focused Dataset remains compatible with the rest of the AgentX vehicle family.

The smallest useful billed run is one published result assuming the minimum one $0.01000 Actor Start event, totaling $0.01550 with the $0.00550 FREE-tier row.

  • Focused source selection: Every request targets Autotrader, so downstream data does not need another platform filter.
  • Required user intent: country, keyword, and max_results stay explicit in each run input.
  • Optional regional scope: Supply a city or ZIP for a native radius, or omit location to avoid inserting a geographic default.
  • Normalized vehicle data: Analyze prices, mileage, vehicle details, seller context, images, and identifiers through 37 fields.
  • Direct verification: Keep source_url and listing_id beside each row for review and deduplication.

The official Autotrader search page shows the source's live public inventory interface; filters, displayed attributes, and availability remain source-controlled.

Quick Start Guide

Configure

Enter keyword=Chevrolet Tahoe, country=United States, and max_results=3. Optional filters stay omitted unless they represent the user's intended request.

Run

Start the Actor in Console. Keep country=United States explicit even when this focused source route accepts only that market.

Collect

Open the Dataset and review title, price, currency, mileage, platform, and source_url before exporting JSON, CSV, Excel, XML, or RSS.

Input Parameters

AutoTrader Vehicle Search accepts 4 public input properties in schema order; max_results, country, and keyword remain required on every edition.

ParameterTypeRequiredDescriptionExample
max_resultsintegerYesMaximum published rows; minimum 1.3
countrystringYesRequired shared selector with 28 schema options; this edition's effective market is United States.United States
keywordstringYesVehicle phrase passed to the source without translation or replacement.Chevrolet Tahoe
locationstringNoUS city or ZIP; a resolved ZIP applies the source-native 50-mile radius.Omitted

When location resolves to a US ZIP, the request uses a native 50-mile source radius. Omit it when geographic filtering is unnecessary.

Use this same scenario throughout the examples:

{
"max_results": 3,
"country": "United States",
"keyword": "Chevrolet Tahoe"
}

No optional request-affecting filter is injected when its field is omitted. This keeps geography and source scope under the user's control.

Output Data Schema

Each Dataset item is one normalized public vehicle record with 37 documented fields. Missing source values remain null or empty rather than being inferred.

FieldTypeMeaning
main_imagestring or nullPrimary image URL.
titlestring or nullListing title.
pricenumber or nullParsed numeric asking price.
currencystring or nullOriginal listing currency.
yearinteger or nullVehicle model year.
makestring or nullVehicle make.
modelstring or nullVehicle model.
trimstring or nullTrim or variant.
mileageinteger or nullParsed mileage.
mileage_unitstring or nullMileage unit.
locationstring or nullPublished listing location.
latitudenumber or nullPublished latitude.
longitudenumber or nullPublished longitude.
countrystring or nullListing country or region.
platformstring or nullSource marketplace.
source_urlstring or nullDirect source URL.
sellerstring or nullSeller or dealer name.
seller_typestring or nullSeller type.
conditionstring or nullVehicle condition.
body_typestring or nullBody type.
seatsinteger or nullSeat count.
fuelstring or nullFuel or powertrain.
transmissionstring or nullTransmission.
enginestring or nullEngine details.
drive_typestring or nullDrivetrain.
exterior_colorstring or nullExterior color.
interior_colorstring or nullInterior color.
vinstring or nullVIN when available.
listing_idstring or nullSource listing identifier.
posted_atstring or nullSource posted date.
updated_atstring or nullSource updated date.
descriptionstring or nullListing description.
imagesarrayImage URLs.
price_textstring or nullOriginal price text.
official_urlstring or nullSeller or dealer URL.
processorstring or nullActor URL that processed the row.
processed_atstring or nullUTC processing timestamp.

This abbreviated JSON example shows the scenario's row shape; the full Dataset contract contains all 37 fields, and the images array is shortened for readability:

{
"main_image": "https://example.com/vehicle.jpg",
"title": "2021 Chevrolet Tahoe",
"price": 46990,
"currency": "USD",
"year": 2021,
"make": "Chevrolet",
"model": "Tahoe",
"mileage": 42000,
"mileage_unit": "mi",
"location": "United States",
"country": "United States",
"platform": "Autotrader US",
"source_url": "https://www.autotrader.com/cars-for-sale/all-cars",
"seller": "Example dealer",
"condition": "Used",
"listing_id": "source-listing-id",
"images": [
"https://example.com/vehicle.jpg"
],
"price_text": "USD 46990",
"processor": "https://apify.com/agentx/autotrader-vehicle-search",
"processed_at": "2026-08-10T08:00:00Z"
}

Use source_url for verification, pair price with currency, and retain processed_at when comparing observations. The Actor does not convert currencies or turn asking prices into completed-sale prices.

Integration Examples

Use Actor ID twOhmfRN7EGJmymoU or name agentx/autotrader-vehicle-search with the same Chevrolet Tahoe scenario in every integration.

Actor ID

twOhmfRN7EGJmymoU

The stable name form is agentx/autotrader-vehicle-search.

HTTP API

curl -X POST "https://api.apify.com/v2/acts/twOhmfRN7EGJmymoU/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"max_results":3,"country":"United States","keyword":"Chevrolet Tahoe"}'

Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("twOhmfRN7EGJmymoU").call(run_input={"max_results":3,"country":"United States","keyword":"Chevrolet Tahoe"})
items = list(client.dataset(run["defaultDatasetId"]).iterate_items())
print(items)

JavaScript

import { ApifyClient } from "apify-client";
const client = new ApifyClient({ token: "YOUR_APIFY_TOKEN" });
const run = await client.actor("twOhmfRN7EGJmymoU").call({"max_results":3,"country":"United States","keyword":"Chevrolet Tahoe"});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Make.com

  1. Add an Apify Run an Actor module and paste Actor ID twOhmfRN7EGJmymoU.
  2. Provide {"max_results":3,"country":"United States","keyword":"Chevrolet Tahoe"} as the JSON input.
  3. Add Get Dataset Items using the returned default Dataset ID.
  4. Map title, price, currency, platform, and source_url into the destination module.

n8n

  1. Add an HTTP Request node with method POST.
  2. Call https://api.apify.com/v2/acts/twOhmfRN7EGJmymoU/run-sync-get-dataset-items with Apify token authentication.
  3. Send {"max_results":3,"country":"United States","keyword":"Chevrolet Tahoe"} as the JSON body.
  4. Process title, price, currency, listing_id, and source_url from each returned item.

MCP

Ask an Apify MCP-connected agent: “Run agentx/autotrader-vehicle-search with {"max_results":3,"country":"United States","keyword":"Chevrolet Tahoe"}. Return title, price, currency, platform, and source_url, and do not invent missing values.”

Pricing

AutoTrader Vehicle Search costs $0.00550 per published result on FREE plus the minimum one $0.01000 Actor Start event, so the smallest one-result run totals $0.01550.

TierActor StartPublished result
FREE$0.01000$0.00550
BRONZE$0.01000$0.00495
SILVER$0.01000$0.00440
GOLD$0.01000$0.00413
PLATINUM$0.01000$0.00413
DIAMOND$0.01000$0.00413

Each Actor Start event costs $0.01000, and the number charged depends on Actor memory: one event per GB, with a minimum of one. The result event is billed once per published Dataset row. Assuming the minimum one Start event, a typical 10-result FREE-tier run costs $0.01000 + 10 × $0.00550 = $0.06500. One 10-result request avoids nine minimum Start events; ten separate one-result runs with one Start event each would total $0.15500 on FREE. A zero-result run can still incur Actor Start. Prices can change; check the live pricing page before budgeting a larger workflow.

Use Cases

  • Asking-price research: Group make, model, year, price, currency, and platform for a defined vehicle set.
  • Dealer inventory review: Organize public records by seller, seller_type, location, official_url, and source_url.
  • Availability monitoring: Schedule the same input and compare listing_id, posted_at, updated_at, and price fields.
  • Specification analysis: Measure coverage for fuel, transmission, engine, drive_type, body_type, and seats.
  • Listing review queues: Send title, description, main_image, images, and source_url to a human validation step.

These workflows should treat each Dataset row as an observation of a public listing, not proof that a vehicle remains available or that an asking price became a completed sale.

Alternatives

For a one-time interactive search, the official Autotrader page is the simpler path and preserves its live consumer controls. A hand-maintained spreadsheet can also be appropriate for a tiny, non-recurring study. AutoTrader Vehicle Search is useful when Autotrader results must become repeatable JSON or tabular output for automation.

Generic browser automation is more flexible for custom page actions but requires the workflow owner to design extraction, normalization, retries, exports, and provenance. Choose something else if you need logged-in services, private dealer feeds, completed transaction prices, financing decisions, inspections, vehicle-history reports, or guaranteed VIN coverage.

Limits and Troubleshooting

  • The query returns no rows → The public inventory may have no current match or the source may be temporarily unavailable. Broaden the phrase and retry later.
  • A city does not narrow results → Use an explicit five-digit US ZIP when an ambiguous place name cannot be resolved.
  • Fewer rows arrive than requested → max_results is a ceiling, not a guarantee; public availability determines the final count.
  • Some fields are empty → Sources vary by listing. Treat null as unavailable and verify important facts with source_url.
  • A listing changes after collection → Public inventory is time-sensitive; retain identifiers, timestamps, currency, and the direct URL.

For a reproducible problem, open the Actor Issues page and include the run ID, exact JSON input, expected result, and one relevant source URL.

Trust and Reliability

  • Apify execution: Runs, schedules, storage, API access, and integrations use the Apify platform.
  • Event-based billing: Metadata defines memory-scaled Actor Start events and one primary result event per published item.
  • Documented contract: The Dataset schema defines exactly 37 fields with types, descriptions, and examples.
  • Source-values-only policy: Missing marketplace attributes remain null or empty; VINs, seller facts, and prices are not manufactured.
  • Row provenance: platform, source_url, listing_id, and processing timestamps support review and downstream deduplication.

Reliability still depends on a public source being reachable and returning qualifying listings for the supplied phrase. Consumers should monitor row counts, retain retry logic, and validate high-impact decisions against the source URL.

Public data scope: The Actor is designed for publicly accessible vehicle listing information. It does not grant access to private accounts, dealer systems, or restricted feeds.

Privacy and purpose: Review whether seller or location fields contain personal information, collect only what the workflow needs, and apply suitable retention and access controls.

Terms and responsibility: Follow Apify terms, the source platform's terms, applicable robots rules, and local law. You are responsible for collection frequency, volume, storage, and use.

Frequently Asked Questions

Is this an autotrader car listings scraper?

Yes. AutoTrader Vehicle Search turns the requested public vehicle search into normalized Apify Dataset rows.

Can I scrape autotrader vehicle listings by ZIP?

Yes. Set location to a US ZIP to request the native 50-mile source radius.

Which inputs are required?

max_results, country, and keyword are required. Any exposed location field remains optional. Fixed routing never authorizes removing the shared required country input.

Does max_results guarantee the requested row count?

No. It caps output, while current public inventory and qualifying records determine how many rows are published.

Is there a free vehicle listings API?

The Actor has a FREE tier, but Actor Start and published result events still carry the listed charges.

Can I schedule vehicle inventory monitoring?

Yes. Use Apify schedules and compare listing IDs, prices, timestamps, currencies, and source URLs between Datasets.

Does every row contain every field?

No. The schema is stable, but a field remains null or empty when the source did not provide a value.

AgentX currently has 79 Actors; this section lists the three closest vehicle workflows first, followed by the complete generated catalog by category.

Closest to this Actor:

Business and Market Intelligence

Jobs and Hiring

Social Media

Video, Transcripts and Downloads

E-Commerce and Retail

Classifieds and Automotive

Real Estate

Support and Community

Ask about Autotrader searches, vehicle fields, and Dataset integrations in the AgentX community on Telegram; for a reproducible bug, open an Issue with the run ID and the exact input.

AgentX is an Arcyton brand — arcyton.com.

Last Updated: August 10, 2026