AutoScout24 Vehicle Listings, Delivered as API Data
AutoScout24 listing pages depend on JavaScript and active bot detection, which makes a plain HTTP fetch unreliable and a self-managed headless browser stack expensive to maintain.
This hosted scraping API takes an AutoScout24 URL, renders the page in a real headless browser, handles anti-bot measures, and returns either the post-render HTML or structured JSON. Your client stays a thin HTTP call.
What you can pull from AutoScout24
The API is aimed at the data teams most often need from vehicle marketplaces: pricing, full listing specifications, and image data. Per listing, the documented fields include make, model, year, mileage, transmission, fuel type, listing price, dealer name, country, and the photo gallery. VINs and dealer information are also listed among the parsed outputs.
Typical uses:
- Competitor price tracking and market trend analysis across European markets AutoScout24 covers.
- Side-by-side market research, for example comparing AutoScout24 listings with Mobile.de.
- Building product or inventory representations from listing images and specs.
How the request flow works
- Create an account to get an API key and free starting credits.
- Install an SDK for Python, Node, Go, PHP, Ruby, or Java, or use plain cURL. Each scrape becomes a single function call.
- POST or GET the AutoScout24 URL to the API. The service renders the listing page, handles anti-bot measures, and returns rendered HTML by default.
- Add parameters when needed: render_js for JavaScript execution, stealth_proxy for CAPTCHA-heavy pages, country_code for geo-targeting, and extract_rules or ai_extract_rules for structured JSON.
The dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby, or cURL before dropping it into your codebase.
Choosing an output mode
The API supports three practical output shapes for AutoScout24 work:
- Rendered HTML: the post-render page markup. Best when you want to parse with your own selectors or archive the page.
- Structured JSON via extract_rules: map CSS selectors to field names and receive parsed JSON. Best for stable, repeatable field sets.
- Structured JSON via ai_extract_rules: describe the fields you want in natural language. Best when the page structure shifts or you are exploring a new field set.
A screenshot mode is also available for capturing how a real browser renders a page, and a Markdown/plain-text mode can format page content for downstream analysis.
Field and control map
Use this map to plan a request before you write code.
| Need | Request control | Output |
|---|---|---|
| JavaScript-rendered listing page | render_js=true | Post-render HTML |
| CAPTCHA-heavy page | stealth_proxy | Rendered response |
| Country-specific content | country_code | Response routed via that country's residential IP |
| Fixed field set | extract_rules (CSS selectors mapped to field names) | Parsed JSON |
| Exploratory field set | ai_extract_rules (natural-language spec) | Parsed JSON |
| Visual check | screenshot option | Full-page screenshot |
| Readable text | Markdown/plain-text mode | Formatted content |
Listing fields commonly returned: make, model, year, mileage, transmission, fuel type, listing price, dealer name, country, photo gallery, VIN.
Worked example: one listing page to JSON
Suppose you want the price, mileage, and dealer for a single AutoScout24 listing. A minimal request would:
- Target the listing URL.
- Set render_js=true so the JavaScript-rendered page is executed server-side.
- Pass extract_rules mapping CSS selectors to field names such as price, mileage, and dealer.
- Receive parsed JSON in the response.
If the selectors break after a site change, switch to ai_extract_rules with a natural-language description of the same fields. If the page is geo-sensitive, add country_code so the request routes through a residential IP in that country.
Telling failure modes apart
Three different problems can look similar in logs:
- Concurrency limits: the API enforces concurrency limits per plan, not per-target rate limits. If you hit them, reduce parallel requests or move to a plan with higher concurrency.
- Target throttling: if AutoScout24 itself throttles aggressive patterns, space out requests or use multiple sessions.
- Geo-variance: if content differs by country, the fix is country_code rather than retries.
Separating these early avoids tuning the wrong control.
Plans and credit mechanics
Plans are billed monthly and differ in API credits, concurrent requests, and support features. The captured plan table below preserves the original rows and figures exactly; treat them as a dated reference and confirm current pricing before purchase.
Credit rules that affect AutoScout24 work:
- API credits are valid for one month and do not roll over. Requests start at 1 credit each.
- Each successful request that enables JS rendering costs 5 API credits.
- Each successful request that enables Premium proxies costs 10 or 25 API credits, depending on whether JS rendering is disabled or not.
- Geotargeting routes through 200+ countries and territories (40+ on classic proxies).
- Screenshots and extraction rules are available on all listed plans.
- Team management lets you invite users and assign custom credit and concurrency quotas.
All prices are exclusive of VAT.
Related capabilities
Beyond raw listing pages, the same platform supports AI-powered extraction, full-page screenshots, Google search result extraction, JavaScript scenarios (click, scroll, wait, custom JS), Markdown/plain-text output, and no-code automation through n8n. These are separate features rather than AutoScout24-specific endpoints, but they are commonly combined with listing scrapes.
Data handling and compliance posture
The provider states that it does not collect or store personal data from scraped sites unless the user explicitly requests it, and describes the service as GDPR and CCPA compliant. Proxy rotation and headless browser rendering are used to reduce IP-based blocking and mimic real user browsing behavior. These statements describe the provider's posture; your own legal review of the target site's terms and applicable law remains necessary.
| Plan | Price / month | API credits | Concurrent requests | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 | 250,000 | 50 | Not included | Not included | Not included |
| Startup (Recommended) | $99 | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 | 120,000,000 | 900 | Included | Included | Included |
All prices are exclusive of VAT. JavaScript rendering, rotating & premium proxies, geotargeting, and screenshots & extraction rules are included on every listed plan. Figures are a dated reference; confirm current pricing before purchase.
Frequently asked questions
Can I scrape AutoScout24 without writing code?
Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL.
How do I handle JavaScript when scraping AutoScout24?
Pass render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and the post-render HTML is returned.
Can I scrape AutoScout24 from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geo.
What's the rate limit for scraping AutoScout24?
There is no per-target rate limit; instead, each plan caps how many requests can run at once. If AutoScout24 starts throttling aggressive patterns, slow the request cadence or spread the work across multiple sessions.
How do I get structured JSON from AutoScout24?
You have two routes to parsed JSON: supply extract_rules that pair CSS selectors with the field names you want, or supply ai_extract_rules describing the fields in natural language. Either way, the response body arrives already parsed as JSON.
Which programming languages can I use to scrape AutoScout24?
Any. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java. Plain cURL works too. Pick whatever your stack already uses.