Autoscout24 is blocking you. What the Autoscout24 API has to get past

Building an Autoscout24 API is not mainly an extraction problem. The challenge is getting a response worth extracting from, then doing it again on a schedule without waiting for a human to notice the system broke.

Here is what our own Autoscout24 Actor handles, how much a run costs, and where it stops.

Doing it yourself

The DIY route makes sense when you need a single snapshot or when a failed run costs you nothing. In practice, it involves the following work — these specifics come directly from what our own scraper has to handle.

The front door. When measured on 2026-08-22, Autoscout24 served a plain request normally (200, nginx). Getting the page is not the difficult part. Keeping pagination and parsing operational is.

Getting past the gate. Autoscout24's bot protection rejects requests before they reach a page handler, leaving the 403 without a useful body. Ours re-mints the cookie after the first one. A client that keeps retrying the same cookie will receive the same 403 forever.

Rate limits. Above a certain request rate, Autoscout24 stops returning data and responds with 429. Testing for that limit can consume the run already in progress.

Proxies. Anonymity is not the main reason to rotate proxies here. Request shape is. Traffic sent to Autoscout24 from one address arrives in an order no human would produce. Expect the proxies to cost more than the compute.

Pagination. The obvious loop keeps requesting pages until nothing comes back. That works when the list is finished, but it also stops silently after a soft block. The output does not reveal which one happened.

Silent breakage. Do not plan only for crashes. Autoscout24 can ship new markup, the parser can match nothing, and every later run can still return well-formed records full of holes.

Deduplication. Without state between runs, the second run costs as much as the first while telling you nothing new. The cheapest fix is a stored hash for each record.

The real cost is upkeep. The first version takes an afternoon to write. After that, keeping it operational takes an hour every few weeks, forever. Failures stay quiet: you discover them when a report is empty, not when the scraper throws an error.

These figures come from a measured run, not an estimate:

• 300 records in 157.7 seconds
• cost: $0.0033 — about $0.01 per 1,000 records

The shortcut

If you do not want to own that work, the same result takes one call:

```bash curl -X POST "https://api.apify.com/v2/acts/blackfalcondata~autoscout24-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \ -H 'Content-Type: application/json' \ -d '{"make": "..."}' ```

The Python version is:

```python from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN") run = client.actor("blackfalcondata~autoscout24-scraper").call(run_input={"make": "..."})

for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) ```

What comes back

Each record contains 74 fields, grouped into categories such as:

• seller — sellerType, sellerName, sellerContact, sellerPhone, sellerRatingStars, sellerRatingCount
• price — price, priceFormatted, priceEur, priceNegotiable, priceEvaluation
• model — model, modelGroup, modelVersion, modelCode

What people use it for

• Benchmarking. Pricing and salary fields allow comparisons across the entire set instead of relying on a page of results.
• Reputation monitoring. Ratings and review text tracked over time reveal movement that one page view cannot show.
• Lead lists. Company-level fields let teams filter for the relevant segment before anyone opens a CRM.
• Change detection. Timestamps support run-to-run diffs, so teams can act on new information instead of reading everything again.
• Geographic analysis. Location fields enable market-by-market comparisons without requiring another data source.

What it will not do

• Nothing here gets you past a Autoscout24 login. Public pages only, whoever writes the scraper.
• A scraper that works today may not work in six weeks. The failure mode is silence, not an exception.
• Proxy cost grows with volume, and it is the line item people routinely overlook when estimating the DIY route.

Questions people ask

Is scraping Autoscout24 legal?

Reading publicly visible pages is generally treated differently from accessing data behind a login. Courts in the US have repeatedly declined to treat public scraping as unauthorised access. That is not legal advice, and a site's terms of service remain a separate question from the law. Anything behind a login is out of scope either way.

Why am I getting 403s when the page loads fine in my browser?

The check is not about the URL. A plain request to Autoscout24 from our probe on 2026-08-22 was answered by aws cloudfront — 0 of 3 attempts were refused. A browser passes because it supplies a TLS fingerprint, a cookie and a header set that a bare HTTP client lacks.

Do I need proxies?

For anything beyond a small sample, yes. Our own input exposes `proxyConfiguration` because a single origin IP is the easiest thing in the world to rate-limit.

How often will it break?

Plan to touch it whenever Autoscout24 releases a redesign. Also expect the problem to go unnoticed for a while: extraction fails quietly and returns empty fields instead of errors. Budget an hour every few weeks, not a fix-and-forget afternoon.

Is it cheaper to build it myself?

Only if your time is free. The measured run below cost $0.0033 for 300 records. The equivalent DIY cost includes proxy spend and the maintenance hour, and that maintenance hour recurs.

Try it

If you do not want to own the upkeep, the Autoscout24 API we keep working already handles everything above. New accounts receive $5 of free platform credit each month, enough to cover a real run of this size several times over.

Disclosure: we build and maintain this Actor, and the link above is an affiliate link.

Further reading

• hiQ Labs v. LinkedIn — the appeals decision on scraping public pages
• Apify's API reference — the endpoints used above
• dataset storage — how results are stored and exported
• Wellfound API — another scraper we build and document
• the Upwork API, in the same detail — another scraper we build and document
• our write-up on the Internshala API — another scraper we build and document

We also publish our write-up on the Autoscout24 API on blackfalcondata.com — the request, the response, and what a run costs.