Gaspedaal.nl Scraper — Dutch Used Car Listings, Prices & Dealer Data

Scrape used car listings from Gaspedaal.nl, the Netherlands' largest used car search aggregator, owned by ANWB (the Dutch automobile association). Extract prices, mileage, fuel type, transmission, year, colour, and dealer details for any brand and model.

What is Gaspedaal.nl?

Gaspedaal.nl aggregates used car listings from dealers across the Netherlands into a single searchable index — similar in role to AutoScout24 in Germany or AutoTrader in the UK, but focused entirely on the Dutch market. It does not host its own classifieds; it indexes dealer inventory and points buyers to the seller. If a used car is for sale by a Dutch dealer, it is very likely indexed on Gaspedaal.

This actor reads the site's own structured data (embedded JSON-LD ItemList blocks) directly from the search-result HTML, so results are exactly what Google sees and exactly what the site itself publishes as the source of truth for each listing. What you can build with it:

• Market valuation — estimate fair asking prices for a specific make, model and year by pulling live listings across the Dutch market.
• Price trend tracking — schedule weekly runs for a model and compare price/mileage distributions over time.
• Dealer intelligence — see which dealers carry the most stock for a given brand, and how their pricing compares.
• Inventory sourcing — used car exporters and traders scanning for underpriced or specific-spec vehicles.
• Insurance / financing calibration — insurtechs and lenders benchmarking Dutch used car values.

What data does Gaspedaal Scraper extract?

Each car listing includes:

• Title — the full listing headline (trim, engine, notable options)
• Brand and model — normalised from the site's own structured data
• Body type — Hatchback, SUV, Sedan, Stationwagen, etc.
• Fuel type — Benzine, Diesel, Hybride, Elektrisch, LPG
• Year — production year
• Mileage — kilometres on the odometer
• Transmission — Automaat or Handmatig
• Colour and number of doors
• Price and currency (always EUR)
• Stock status — whether the listing is currently marked available
• Dealer name, dealer link, city and region
• Image URL
• Listing URL — anchor link to the exact listing on the Gaspedaal search-result page

How to scrape Gaspedaal data

Field	Type	Required	Description
brand	String	No	Car brand slug, e.g. "volkswagen", "audi", "bmw" (default: "volkswagen")
model	String	No	Car model slug, e.g. "golf", "a3", "x5" (default: "golf"). Leave empty to auto-discover and crawl up to 12 models for the brand
maxResults	Integer	No	Maximum listings to return (default: 100, max: 5,000)
minYear / maxYear	Integer	No	Restrict to a production-year range
fuelType	String	No	benzine, diesel, hybride, elektrisch, or lpg
minPrice / maxPrice	Integer	No	Restrict to a price range (EUR)
maxMileage	Integer	No	Only return cars at or below this mileage (km)
proxyConfiguration	Object	No	Proxy settings — optional, the site has no bot protection

Tips:

• Brand and model use the site's own URL slugs. If unsure, browse gaspedaal.nl/{brand}/{model} in a browser first — whatever appears in the address bar is the slug to use.
• Leave model empty to fan out across a brand's model lineup automatically.
• Combine minYear/maxYear with a high maxResults to pull deep, specific slices (e.g. every 2018-2020 Golf) rather than just the newest 100 listings.
• fuelType, minPrice, maxPrice and maxMileage keep the crawl running across the site's filter pages until maxResults is reached or every reachable page is read. A narrow filter therefore costs more requests than a wide one.
• The run log ends with the number of listings returned, the number of unique listings read, and the total the site lists for that search. Use those three numbers to see how much of the search you got.

Output

{
    "listingId": "138767501",
    "listingTitle": "Volkswagen Golf - 1.4 TSI GTE | Trekhaak | Carplay",
    "brand": "Volkswagen",
    "model": "Golf",
    "bodyType": "Hatchback",
    "fuelType": "Hybride",
    "year": 2016,
    "mileage": 121210,
    "transmission": "Automaat",
    "color": "Wit",
    "numberOfDoors": 5,
    "price": 14750,
    "currency": "EUR",
    "inStock": true,
    "dealerName": "Onbekende dealer",
    "dealerUrl": "https://www.gaspedaal.nl/autobedrijven/vakgarage-middenpeel/aanbod",
    "city": "Ysselsteyn",
    "region": "Limburg",
    "imageUrl": "https://cdn.gaspedaal.nl/images/large/645c615d....jpg",
    "url": "https://www.gaspedaal.nl/volkswagen/golf#138767501",
    "searchBrand": "volkswagen",
    "searchModel": "golf",
    "scrapedAt": "2026-08-05T19:39:17.029Z"
}

Coverage & limitations

Gaspedaal.nl serves 100 listings per URL and its robots.txt blocks query-string pagination (Disallow: /*?, with an allowlist that does not cover /{brand}/{model}?page=N). This actor is robots-compliant and never uses ?page=. To get past the 100-per-URL ceiling it fans out over the site's own path filter pages, which carry no query string and are listed in the site's sitemaps:

• production years, e.g. /volkswagen/golf/2016
• generations and trims, e.g. /volkswagen/golf/7-gti, /volkswagen/golf/r-line
• colours, body types, fuel types and gearbox, e.g. /volkswagen/golf/zwart, /volkswagen/golf/stationwagen, /volkswagen/golf/diesel, /volkswagen/golf/automatisch

Listings are deduplicated across slices, so a car that appears in three filter pages is returned once.

What this means for coverage:

• Searches with up to a few hundred listings are returned in full.
• Large searches are capped by what the filter pages expose. Measured on 16 September 2026: /volkswagen/golf lists 6,829 cars, and reading all 79 of its filter pages returns 3,012 unique cars. Every filter page serves its own first 100 listings, so the cars beyond position 100 in every single filter page cannot be reached without ?page=.
• The site's filter pages cannot be combined. /volkswagen/golf/2016/diesel returns 404, so a fuel search is widened by reading the year, trim and colour pages and matching fuel on the data.
• There is no price or mileage filter page on the site, so minPrice, maxPrice and maxMileage are applied to the data after fetching. The crawl keeps reading filter pages until maxResults is reached or the pages run out.
• A run reads at most 150 pages. The run log says when that budget stopped it early.
• Gaspedaal has no standalone per-listing detail page — clicking a listing redirects to the dealer's own site (a path disallowed in robots.txt). The url field is the listing's anchor on the Gaspedaal search-result page, which is stable and unique per listing.

How much does it cost?

Cost estimate: $0.002 per result (pay-per-result pricing, lower on higher Apify plans). The actor makes one plain HTTP request per filter page of up to 100 listings — no browser rendering, no anti-bot bypass needed.

What you ask for	Pages read	Estimated cost
100 cars, no filters	1	~$0.21
500 cars, no filters	~6	~$1.01
1,000 cars, no filters	~12	~$2.01
A narrow filter (one fuel type under a price cap)	up to 150	billed per matching result, so a narrow search costs little

Usage cost only settles once a run finishes with status SUCCEEDED — a run that fails or is aborted early does not bill for partial results.

Can I integrate?

Feed Dutch used car data into your systems:

• Google Sheets — maintain a live inventory tracker for a specific brand and model
• Slack — alert on underpriced listings matching your criteria
• Zapier / Make — automate price-monitoring workflows
• PostgreSQL / BigQuery — build a historical Dutch used car price database
• Power BI / Tableau — visualise market trends and price distributions

Can I use it as an API?

Yes. Build Dutch car market intelligence into your products:

Python:

from apify_client import ApifyClient

client = ApifyClient("YOUR_API_TOKEN")

run = client.actor("studio-amba/gaspedaal-scraper").call(run_input={
    "brand": "volkswagen",
    "model": "golf",
    "maxResults": 300,
})

for car in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(f"{car['listingTitle']} - EUR {car['price']} | {car.get('mileage', '?')} km | {car.get('year', '?')}")

JavaScript:

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: "YOUR_API_TOKEN" });

const run = await client.actor("studio-amba/gaspedaal-scraper").call({
    brand: "volkswagen",
    model: "golf",
    maxResults: 300,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((car) => {
    console.log(`${car.listingTitle} - EUR ${car.price} | ${car.mileage || "?"} km`);
});

FAQ

Does this cover new cars too? No, Gaspedaal.nl (and this actor) covers used/second-hand cars only.

Can I search by keyword instead of brand/model? The site is structured by brand and model URLs rather than free-text search, so this actor takes brand/model inputs. Leave model empty to sweep an entire brand's lineup.

Why do some runs return fewer than maxResults? If a brand/model/filter combination has fewer live listings than requested, or the request budget (60 requests/run) is exhausted while filters are excluding most results, the run returns whatever it found. Check the run log for the "listed X total on this slice" lines to see actual site inventory.

Does it include dealer contact details? Dealer name, city and region are extracted. Direct phone/email is not published on the aggregator listing itself — that lives on the dealer's own site, one click away via dealerUrl.

How current are the listings? Gaspedaal reflects live dealer inventory. Cars that sell get removed from the index within days. Schedule weekly runs to track market changes.

Is proxy required? No. Gaspedaal.nl has no bot-detection wall. Proxy is available in the input for reliability on larger runs but is not required for normal use.

Related car and Dutch market scrapers

• AutoScout24 Scraper — pan-European used car listings, including the Netherlands
• Marktplaats Scraper — the Netherlands' largest classifieds site, including private-seller cars
• Funda Scraper — Dutch real estate listings
• AutoVlan / GoCar Scraper — Belgium's largest used car marketplace

Your feedback

Want support for additional filters, historical price tracking, or found a parsing issue? Open an issue on GitHub or contact us through the Apify platform. Your feedback drives what we build next.