Mobile.de Dealer Leads Scraper

Turns Mobile.de — Europe's largest vehicle marketplace — into a B2B lead list of German car dealers: one clean row per dealer, with the e-mail, phone, address, VAT ID, star rating and live inventory already joined together.

It reads Mobile.de's own regional dealer directory (home.mobile.de/regional/), which is organised by federal state → city, so you enumerate dealers directly instead of guessing at them from car adverts.

---

What one row looks like

{
  "source": "mobile.de",
  "dealerId": "45655133",
  "companyName": "Autoboutique Stuttgart GmbH",
  "email": "konstantin@autoboutique.io",
  "phone": "+4971125089501",
  "whatsapp": null,
  "website": null,
  "street": "Stockholmer Platz 1",
  "zip": "70173",
  "city": "Stuttgart",
  "countryCode": "DE",
  "latitude": 48.7897069,
  "longitude": 9.1838239,
  "vatId": "DE457995887",
  "ratingScore": null,
  "ratingCount": null,
  "contactLanguages": ["de"],
  "memberSince": "7 Monaten",
  "inventoryCount": 1,
  "brands": ["Mercedes-Benz"],
  "priceMin": 173000,
  "priceMax": 173000,
  "inventorySampleComplete": true,
  "description": null,
  "imprint": "Autoboutique Stuttgart GmbH Stockholmer Platz 1 70173 Stuttgart Deutschland …",
  "dealerPageUrl": "https://home.mobile.de/AUTOBOUTIQUESTUTTGARTGMBH",
  "enriched": true,
  "province": "Baden-Württemberg",
  "cityQueried": "Stuttgart",
  "makeQueried": null,
  "scrapedAt": "2026-09-09T15:54:03.556Z"
}

field	what it is
dealerId	Mobile.de's own dealer id — the stable dedup key
companyName	Registered dealer / company name
email · phone · whatsapp	Contact block from the dealer's own page. Phone and WhatsApp are normalised to E.164
website	The dealer's own site, where they publish one
street · zip · city · countryCode	Full postal address
latitude · longitude	Geo-coordinates, for radius filtering and mapping
vatId	German VAT ID (USt-IdNr.) from the statutory Impressum
ratingScore · ratingCount	Mobile.de star rating and how many reviews it is built on
contactLanguages	Languages the dealer will take enquiries in
memberSince	How long they have sold on Mobile.de (as Mobile.de phrases it, e.g. "10 Jahren")
inventoryCount	Vehicles the dealer has live right now
brands · priceMin · priceMax	Makes stocked and the price band — from a sample, see below
inventorySampleComplete	true only when that sample covered the dealer's whole live inventory
imprint	Raw Impressum text (managing director, register number, VAT)
enriched	true if the dealer's own page was read; false means the contact columns were not read, not that they are empty
province	The federal state the dealer's directory listing sits in — the real state even on an All Germany run, null only for a nationwide make filter, whose payload carries no state

The two honesty flags, and why they are there

enriched — a row can reach you two ways. If the dealer has a Mobile.de dealer page, we fetch it and you get the full contact block. If they publish their own website instead (3–8% of dealers across the measured samples), there is no Mobile.de page to read: you still get name, street, ZIP, city and their website, and enriched is false. A null e-mail on an enriched: false row means not read, never the dealer has no e-mail.

inventorySampleComplete — inventoryCount is Mobile.de's authoritative live total, but brands, priceMin and priceMax are derived from the first page of that dealer's listings (up to 20 vehicles). For a dealer with 46 cars live you get the real 46 in inventoryCount, a price band computed from 20 of them, and inventorySampleComplete: false saying so.

Input

input	default	what it does
province	Baden-Wuerttemberg	Which federal state to scrape, or All Germany to walk all 16 (see the note below)
city	—	Optional single city. Case- and umlaut-insensitive: Munchen, Muenchen and München all find the same place
make	Any	Optional make filter. Mobile.de publishes make-filtered dealer pages for ten makes only: Audi, BMW, Fiat, Ford, Mercedes-Benz, Opel, Peugeot, Renault, Toyota, Volkswagen
maxDealers	100	Cap on unique dealers delivered and billed (0 = whole scope, ceiling 5000/run)
enrichEmails	true	Fetch each dealer's page for contact + inventory. Off = fast directory-only pull
proxyConfiguration	Apify Proxy	RESIDENTIAL, country DE

If you ask for a city or a make Mobile.de does not publish a directory page for, the run tells you what it does list and charges nothing — it never quietly returns the whole state instead.

State values are spelled ASCII (Baden-Wuerttemberg, Thueringen) so API callers never have to worry about UTF-8; the province column in your output carries the proper German name.

All Germany walks the 16 states in order, it does not interleave them. So a run capped below the national total is a complete sample of the first states, not a representative slice of Germany — 45 dealers of "All Germany" are 45 Baden-Württemberg dealers. The status message says how many of the 16 state lists the run actually got to. For a national pull, raise maxDealers (ceiling 5000 per run) or run the states one at a time.

How big is a scope?

Measured live on 2026-09-09 — 35 dealers per directory page throughout:

scope	dealers	pages
Bayern	5,853	168
Baden-Württemberg	4,776	137
Hessen	2,146	62
Berlin	754	22
München (city)	456	14
Stuttgart (city)	142	5
Stuttgart + BMW	12	1

Measured performance

Real runs on the Apify platform through Proxy RESIDENTIAL-DE, re-measured 2026-09-09 — these are the platform's own billed figures, not estimates:

	with enrichEmails	with enrichEmails	500-lead scale run	directory only
scope	Bayern	Baden-Württemberg	Bayern	Hessen
dealers delivered	60	100	500	40
dealers billed	60	100	500	40
wall time	113 s (≈1.9 s per dealer)	191 s	679 s (≈1.4 s per dealer)	13 s (≈0.3 s per dealer)
HTTP responses	60	100	500	3
platform cost, whole run	$0.0384	$0.0844	$0.3985	$0.0019
— of which residential proxy	4.87 MB → $0.0390	8.42 MB → $0.0674	43.1 MB → $0.339	0.07 MB → $0.0005
platform cost per delivered lead	$0.00064	$0.00084	$0.00080	$0.00005
residential KB per delivered lead	81 KB	84 KB	88 KB	1.6 KB
blocks / challenge retries	2 (all recovered)	0	0	0
enrichment failures	0	0	0	—

Cost per lead is flat with scale — $0.00064 at 60 rows, $0.00084 at 100, $0.00080 at 500. The 500-lead run delivered and billed exactly 500, with zero duplicate dealer ids and zero blocks, peaking at 170 MB inside the 1,024 MB container.

Against the $0.005 price, an enriched lead costs about 13–17% of what it sells for; a directory-only lead is essentially free to produce. Small runs are relatively dearer because resolving the scope costs a fixed 2–3 requests: a 5-lead run measured $0.0012 per lead.

Residential proxy is the dominant cost — about 81 KB per enriched lead on the wire, roughly $0.00065 of it. For scale: the same 60-lead Bayern run with the proxy turned off cost $0.0026 in total and finished in 26 s, so the proxy is buying reliability, not data.

The RUN_SUMMARY record also reports response bytes per row (61 KB on that 60-lead run). That counter measures the response payload only — Apify's billed proxy figure is somewhat higher because it also counts the request side and connection overhead. Read the run's usageUsd for actual money.

Field fill rate (same 60-dealer Bayern sample)

field	fill
companyName, street, zip, city	100%
email	92% (100% of the dealers that have a Mobile.de page)
phone	92%
inventoryCount, imprint	92%
latitude / longitude	90%
vatId	75%
ratingScore	57%
website	53%

The 8% shortfall on the enriched columns is the dealers who publish an external website instead of a Mobile.de page — see enriched above. Every dealer that does have a Mobile.de page was read successfully: 55/55 here, 97/97 on the 100-lead run.

Pricing

Pay per event: $0.005 per dealer-lead — charged only for a dealer row actually delivered to your dataset. Deduplication happens before billing, so you are never charged twice for the same dealer in a run, and a run that returns nothing costs nothing.

Delivery is budget-aware. Verified on the platform: a run capped at $0.02 delivered 4 leads, billed 4, fetched contact pages for exactly those 4, and reported "Result TRUNCATED by your run budget cap" in its status message; a $0.017 cap delivered and billed 3. Delivered and billed counts matched exactly on every measured run — and if they ever disagree the Actor fails the run rather than reporting success on bad output.

Every run also writes a RUN_SUMMARY record to the key-value store with the scope, delivered vs billed counts, what truncated the result, enrichment success rate and proxy bytes per row.

Proxy

home.mobile.de sits behind Akamai. The Actor defaults to Apify RESIDENTIAL with a DE exit, keeps a cookie jar per session, paces its requests and rotates to a fresh IP on a challenge — that is the configuration these numbers were measured on, and the one to keep unless you have a reason not to.

It is a default, not a hard requirement. Measured on this Actor on 2026-09-09, a residential US exit returned 8 of 8 leads with full contact data, and a run with no proxy at all returned 60 of 60 with 55 e-mails. Akamai can start challenging at any time, so RESIDENTIAL-DE stays the default; but if a run comes back empty the status message tells you which of the two things happened — Mobile.de refused the request, or the proxy itself could not be reached.

Legal

Mobile.de is a public marketplace, and dealer contact details are published by the dealers themselves — very often in the statutory Impressum this Actor also returns. You are responsible for how you use them: for outreach into the EU that means GDPR, and elsewhere the local equivalent.