Harvest Dealer Phone Numbers from Mobile.de Listings

The dealer's phone number is in the search response — almost nobody collects it. Thirdwatch's Mobile.de Scraper queries mobile.de's own search backend and returns complete listing rows — including the dealer phone number that most scrapers can't see.

Skip the setup: Run this as a ready-to-go task on Apify — pre-loaded with the configuration from this guide.

Why harvest dealer contacts

Dealer contact data is lead-generation gold — and on mobile.de it's on the listing itself. Most scrapers never surface it because they parse the HTML card, which doesn't carry it.

Because the Actor reads the search backend, sellerPhone, sellerName, sellerRating and sellerType come back on every dealer row.

Because it reads the search backend directly, rows include fields the HTML listing never exposes — net pricing, VAT flags, KBA type codes, dealer contact data.

How does this compare to the alternatives?

Why this Actor

• Gross AND net price per listing, plus VAT flag — commercial-buyer detail most scrapers miss.
• Dealer phone number, rating and rating count on the row — direct lead-gen data.
• KBA hsn/tsn codes identify the exact variant for valuation work.
• Leasing rate and financing flags included where offered.
• Keyword queries or full filtered search.html URLs — your filters apply exactly.

How to do it in 3 steps

Step 1: Configure the input

Set the inputs as shown below — queries takes the targets, free-text searches work, or paste a filtered searchUrls entry; minPrice, maxPrice and maxMileage bound results server-side.

Step 2: Run the Actor

Run it from the console, the API, or the linked saved task. One dataset row is written per listing.

Step 3: Use the output

Each row carries gross and net price, mileage, registration, fuel, KBA codes, and the dealer's name, rating, and phone number.

{
  "queries": [
    "mercedes c klasse"
  ],
  "maxResults": 25
}

Each dataset row looks like:

{
  "id": "405123456",
  "title": "BMW 320d Touring Sport Line",
  "url": "https://suchen.mobile.de/fahrzeuge/details.html?id=405123456",
  "price": 28900,
  "netPrice": 24285,
  "priceFormatted": "28.900 \u20ac",
  "currency": "EUR",
  "vat": true,
  "mileage": 62000,
  "firstRegistration": "04/2021",
  "fuel": "Diesel",
  "gearbox": "Automatic",
  "power": 140,
  "kbaHsn": "0005",
  "kbaTsn": "BZA",
  "sellerName": "Autohaus Muster GmbH",
  "sellerType": "DEALER",
  "sellerPhone": "+49 30 123456",
  "sellerRating": 4.7,
  "location": "M\u00fcnchen",
  "country": "DE"
}

What to watch for

Search depth is roughly 50 pages per query — for very broad terms, narrow with price/mileage filters or a filtered URL. fetchDetail adds one call per listing; keep it off unless you need the deep fields.

Related use cases

• Snapshot German Car Prices on Mobile.de
• Scan Mobile.de Inside a Strict Price Band
• Find Low-Mileage Value Listings on Mobile.de
• Monitor a Filtered Mobile.de Search on a Schedule
• All Thirdwatch use-case guides

Run the Mobile.de Scraper on Apify Store — pay per result, free to try, no credit card to test.