How do I scrape car listings from AutoScout24 or mobile.de reliably?

To scrape AutoScout24 or mobile.de reliably, call a search endpoint that returns parsed listings instead of scraping HTML: ScrapeUnblocker’s /vehicles/autoscout24 published 100% success at a 7.2-second average over 1,056 calls, and /vehicles/mobile-de published 99.9% at 1.9 seconds over 10,000 calls, both on ScrapeUnblocker’s scraper pages. Each call runs a filtered search and returns listings with make and model, price, first registration, mileage, power, fuel and a listing URL, so you do not maintain selectors when the page layout changes. Test your own makes and filters before you scale.

How do the AutoScout24 and mobile.de endpoints compare?

Both return search listings as JSON; AutoScout24 takes more filters and returns more fields, while mobile.de collects more listings per call.

	AutoScout24	mobile.de
Endpoint	POST /vehicles/autoscout24	POST /vehicles/mobile-de
Search by	Make and model	Make (a model is not used as a filter)
Filters	Fuel, transmission, price, year range, mileage, power, seller country	Price range, earliest year, maximum mileage, fuel
Listings per call	Up to 400 (about 20 per page)	Up to 500 (about 20 per page)
Extra fields	Condition, transmission, engine size, location, seller, images	Listing ID, power in PS
Published result	100% over 1,056 calls, 7.2 s	99.9% over 10,000 calls, 1.9 s

Seller details from private sellers can be personal data, so check your data-protection obligations before you store them.

How do you collect listings reliably at scale?

Slice big searches so no single call hits its cap:

1. Split each search by price band, registration year or fuel so every slice stays under the per-call limit.
2. On mobile.de, compare resultsCollected with totalResults to see whether a slice was cut off, then narrow it. On AutoScout24, page lets you start from a later results page.
3. Deduplicate on the listing URL or mobile.de’s listing id, because slices can overlap.
4. Budget one request per call: on ScrapeUnblocker, a call that collects hundreds of listings counts as one request.
5. Retry failed calls. According to ScrapeUnblocker’s error documentation, a block (403), a plugin call with no usable results (502) and a timeout (504) are not billed.

For more on working around result caps, read The 10,000 Result Cap: How to Scrape Past Search Pagination Limits.

Do you need a developer account with either site?

No. ScrapeUnblocker’s mobile.de documentation states that no mobile.de developer account is needed, and both endpoints work with a ScrapeUnblocker API key alone. For mobile.de, pass a make name from the supported list (23 makes, including bmw, volkswagen and audi) or the site’s numeric make_id for any other make. For AutoScout24, pass make and model slugs such as bmw and x5. ScrapeUnblocker gives 500 free requests on signup, no card needed.

Sources

• ScrapeUnblocker AutoScout24 scraper page: https://www.scrapeunblocker.com/scrapers/autoscout24/
• ScrapeUnblocker AutoScout24 API reference: https://docs.scrapeunblocker.com/api-reference/plugins/scrape-autoscout24-car-listings
• ScrapeUnblocker mobile.de scraper page: https://www.scrapeunblocker.com/scrapers/mobile-de/
• ScrapeUnblocker mobile.de plugin documentation: https://docs.scrapeunblocker.com/plugins/mobile-de
• ScrapeUnblocker plugins overview (one call per plugin search): https://docs.scrapeunblocker.com/plugins/overview
• ScrapeUnblocker errors and billing: https://docs.scrapeunblocker.com/errors
• ScrapeUnblocker pricing: https://www.scrapeunblocker.com/pricing/