Autohero Cars Scraper

Extract Autohero used-car listings from public country search pages.

Autohero Cars Scraper saves prices, mileage, year, trim, fuel, transmission, images, listing URLs, and country metadata.

Use it for inventory monitoring, market pricing research, dealer benchmarking, and lead workflows.

What does Autohero Cars Scraper do?

Autohero Cars Scraper collects vehicle cards from Autohero search result pages.

It works with public Autohero country URLs such as Germany, France, Netherlands, Spain, Italy, and Poland.

The actor parses server-rendered listing HTML.

No login is required for the supported search pages.

Each dataset row represents one car listing.

Who is it for?

Used-car dealers can monitor Autohero inventory in their markets.

Pricing analysts can compare mileage, model year, fuel type, and asking price.

Market researchers can build recurring country snapshots.

Lead-generation teams can export fresh listing URLs.

Data teams can feed normalized vehicle rows into BI dashboards.

Why use this Autohero scraper?

🚗 It is focused on Autohero car cards.

💶 It returns numeric prices and monthly payment text.

📊 It captures mileage, year, fuel, and transmission.

🔗 It includes direct listing URLs for follow-up.

🌍 It supports multiple country search URLs in one run.

What data can you extract?

Field	Description
title	Vehicle card title
make	First token from the title
model	Remaining title text
trim	Autohero subtitle or trim
price	Numeric asking price
priceText	Original displayed price text
monthlyPrice	Numeric monthly payment when shown
monthlyPriceText	Original monthly payment text
year	Registration/model year from specs
fuelType	Fuel type from specs
mileageKm	Numeric mileage in kilometers
transmission	Gearbox/transmission text
co2Emissions	Displayed CO2 value
fuelConsumption	Displayed fuel consumption
badges	Visible badges such as first owner or low mileage
imageUrl	Main listing image URL
listingUrl	Autohero listing URL
country	Autohero country path
sourceUrl	Search URL that produced the listing
scrapedAt	ISO timestamp for the run

How much does it cost to scrape Autohero car listings?

This actor uses pay-per-event pricing.

There is a small start fee per run.

There is a per-listing charge for every car saved to the dataset.

Use a low maxItems value for test runs.

Increase the limit only after your input URLs return the fields you need.

How to use it

1. Open the actor on Apify.

2. Add one or more Autohero search URLs.

3. Set maxItems to the number of car rows you want.

4. Keep deduplication enabled unless you want duplicates across country URLs.

5. Start the run.

6. Export the dataset as JSON, CSV, Excel, or via API.

Input

The main input is startUrls.

Each URL should be an Autohero country or filtered search page.

Examples:

{
  "startUrls": [
    { "url": "https://www.autohero.com/de/search/" },
    { "url": "https://www.autohero.com/fr/search/" }
  ],
  "maxItems": 100,
  "deduplicate": true
}

Output

The actor stores one vehicle per dataset item.

Example output:

{
  "title": "Toyota Yaris Cross",
  "make": "Toyota",
  "model": "Yaris Cross",
  "trim": "1.5 Hybrid AWD-i Premiere Edition",
  "price": 29250,
  "priceText": "29.250 €",
  "monthlyPrice": 402,
  "monthlyPriceText": "402 € mtl.",
  "year": 2024,
  "fuelType": "Hybrid",
  "mileageKm": 7332,
  "transmission": "Automatikgetriebe",
  "listingUrl": "https://www.autohero.com/de/toyota-yaris-cross/id/.../",
  "country": "de"
}

Tips for best results

Copy URLs directly from Autohero after applying filters.

Use separate URLs for separate countries.

Keep deduplicate enabled for multi-country dashboards.

Use maxItems to control spend.

Schedule the actor daily or weekly for monitoring.

Integrations

Send the dataset to Google Sheets for dealer reporting.

Push output to BigQuery for market analysis.

Use webhooks to notify a CRM when new listings appear.

Connect with Make or Zapier for low-code inventory workflows.

Use Apify API clients for automated ingestion.

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/autohero-cars-scraper').call({
  startUrls: [{ url: 'https://www.autohero.com/de/search/' }],
  maxItems: 100,
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient

client = ApifyClient('MY-APIFY-TOKEN')
run = client.actor('automation-lab/autohero-cars-scraper').call(run_input={
    'startUrls': [{'url': 'https://www.autohero.com/de/search/'}],
    'maxItems': 100,
})
print(run['defaultDatasetId'])

API usage with cURL

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~autohero-cars-scraper/runs?token=MY-APIFY-TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"startUrls":[{"url":"https://www.autohero.com/de/search/"}],"maxItems":100}'

MCP usage

Use the Apify MCP server with Claude Desktop or Claude Code.

MCP URL:

https://mcp.apify.com/?tools=automation-lab/autohero-cars-scraper

Claude Code setup:

$claude mcp add apify-autohero "https://mcp.apify.com/?tools=automation-lab/autohero-cars-scraper"

Claude Desktop JSON config:

{
  "mcpServers": {
    "apify-autohero": {
      "url": "https://mcp.apify.com/?tools=automation-lab/autohero-cars-scraper"
    }
  }
}

Example prompts:

• "Scrape 100 Autohero Germany cars and summarize price by fuel type."

• "Run Autohero Cars Scraper for Germany and France and find low-mileage hybrids."

• "Export Autohero listings to a spreadsheet-ready table."

Scheduling

Create an Apify schedule to run the scraper every day.

Use the same filtered URLs each time.

Compare datasets over time to detect inventory and price changes.

Monitoring workflow

Store each run's dataset ID.

Join by listingUrl.

Detect new cars, removed cars, and price movements.

Alert your team when matching cars appear.

Supported pages

The actor targets public Autohero search pages.

It supports country paths such as /de/search/, /fr/search/, /nl/search/, /es/search/, /it/search/, and /pl/search/.

Filtered URLs are supported when Autohero serves listing cards in the initial HTML.

Limitations

The actor does not crawl detail pages in version 0.1.

It extracts fields visible on search result cards.

If Autohero changes its card selectors, extraction may need an update.

Availability can change between a scrape and a user's visit.

Troubleshooting

If you receive fewer rows than expected, increase the number of country or filtered search URLs.

If a filtered URL returns zero rows, open it in a browser and confirm Autohero shows listings.

If prices look localized, use priceText alongside numeric price for display.

Legality

This actor extracts publicly available listing information.

You are responsible for using the data lawfully.

Respect Autohero's terms, privacy rules, and applicable regulations.

Do not scrape personal data or use output for unlawful profiling.

Related scrapers

Explore other Automation Lab actors at https://apify.com/automation-lab/.

Useful adjacent actors may include car marketplace scrapers, e-commerce scrapers, and price monitoring tools.

Support

Open an Apify issue if a supported Autohero search URL stops returning listings.

Include your run ID and input URL.

A small reproducible input helps us fix selector changes quickly.

Changelog

Version 0.1 extracts public Autohero search-card listings from supplied country/search URLs.

FAQ

Can I scrape multiple countries?

Yes. Add multiple Autohero country URLs to startUrls.

Does it require proxies?

The initial implementation uses direct HTTP requests because Autohero search pages returned public SSR HTML during validation.

Can I get listing detail-page fields?

Not in v0.1. Detail-page crawling can be added later if demand justifies the extra cost.

Can I monitor prices over time?

Yes. Schedule recurring runs and compare rows by listingUrl.

Why do some fields show null?

Autohero does not display every spec on every card. Missing card fields are returned as null.