# Doctolib DE Scraper — Doctor & Clinic Directory Data (`studio-amba/doctolib-de-scraper`) Actor

Scrape doctor and healthcare provider listings from Doctolib.de by specialty and city. Get name, specialty, address, coordinates, phone, languages, payment methods, statutory-insurance acceptance, online-booking availability and published fees. Public directory data only, no login required.

- **URL**: https://apify.com/studio-amba/doctolib-de-scraper.md
- **Developed by:** [Studio Amba](https://apify.com/studio-amba) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 result scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Doctolib DE Scraper (doctolib.de)

Scrape public doctor and healthcare-provider listings from Doctolib.de,
Germany's largest healthcare booking platform. Search by medical specialty
and city and get structured provider profiles: name, specialty, address,
coordinates, phone, languages spoken, accepted payment methods, German
statutory-health-insurance ("gesetzliche Krankenversicherung") acceptance
status, online-booking availability, published fees, opening hours, and
services offered.

### Why use this actor?

Health-tech companies, medical marketing agencies, insurance brokers,
patient-acquisition tools, and market-research teams all need up-to-date
lists of practicing doctors by specialty and city. Doctolib is the
dominant such platform in Germany — this actor turns its search results
into a clean, structured dataset instead of manual copy-pasting.

**Compliance note:** every field this actor returns is public professional
directory data that the doctor or clinic chose to publish on their
Doctolib profile — visible to any anonymous visitor and indexed by Google
(the pages carry schema.org `Physician`/`MedicalOrganization` markup
specifically for search-engine indexing). This actor does not collect
patient data, private messages, or any information behind a login.

### Input

| Field | Type | Required | Description |
|-------|------|----------|--------------|
| `specialty` | String | No | Medical specialty in German, as used in the Doctolib URL slug, e.g. `zahnmedizin` (dentist), `allgemeinmedizin` (GP), `augenheilkunde` (ophthalmology), `frauenarzt` (gynecologist), `hautarzt` (dermatologist), `orthopadie`, `urologie`, `neurologie`, `radiologe`. Default: `zahnmedizin` |
| `city` | String | No | German city name. Cities with umlauts need the ASCII-transliterated slug — `muenchen`, not `münchen` or `munich`; `koeln`, `duesseldorf`. Other examples: `berlin`, `hamburg`, `frankfurt-am-main`, `stuttgart`, `leipzig`. Default: `berlin` |
| `maxResults` | Integer | No | Maximum number of healthcare providers to return. Default: `50` |
| `fetchPhoneDetails` | Boolean | No | When `true` (default), visits each provider's profile page for phone number, bio, opening hours and services — one extra request per result. Set `false` for a faster, listing-only run without phone numbers |
| `proxyConfiguration` | Object | No | Proxy settings. Residential proxy is recommended — see Limitations |

If you leave the input empty (`{}`), the actor runs with the defaults above
and still returns real data — useful for a quick test run.

### Output

Each result is one healthcare provider:

| Field | Type | Example |
|-------|------|---------|
| `name` | String | `"Siemer"` |
| `firstName` | String | `"Traute"` |
| `honorific` | String | `"Dr."` |
| `specialty` | String | `"Zahnärztin"` |
| `specialtySlug` | String | `"zahnmedizin"` |
| `providerType` | String | `"INDIVIDUAL_PRACTITIONER"` or `"ORGANIZATION"` |
| `address` | String | `"Schloßstraße 95"` |
| `city` | String | `"Berlin"` |
| `postalCode` | String | `"12163"` |
| `country` | String | `"DE"` |
| `latitude` / `longitude` | Number | `52.4585321` / `13.3225862` |
| `phone` | String | `"030 797 27 00"` |
| `bio` | String | Free-text profile description |
| `languages` | Array | `["de", "gb"]` |
| `paymentMeans` | Array | `["cash", "credit_card"]` |
| `regulationSector` | String | `"akzeptiert_gesetzlich_versicherte_patient"` (accepts statutory health insurance) |
| `onlineBookingAvailable` | Boolean | `true` |
| `minimumFee` | Number | Minimum published consultation fee, where shown |
| `services` | Array | `["Implantologie", "Wurzelkanalbehandlung"]` |
| `openingHours` | Array | `["Mo 08:00-19:00", "Tu 08:00-19:00", ...]` |
| `url` | String | Full Doctolib profile URL |
| `scrapedAt` | String | ISO 8601 timestamp |

Not every field is present on every profile — `phone`, `bio`,
`openingHours` and `services` only populate when `fetchPhoneDetails` is
on, and a share of providers genuinely don't publish a phone number on
their profile (this actor never guesses or fills in a missing number).

### Example output

```json
{
    "name": "Abdulrahim",
    "firstName": "Ziad",
    "honorific": "Dr.",
    "specialty": "Zahnarzt",
    "specialtySlug": "zahnmedizin",
    "providerType": "INDIVIDUAL_PRACTITIONER",
    "address": "Lübbener Straße 21",
    "city": "Berlin",
    "postalCode": "10997",
    "country": "DE",
    "latitude": 52.4993614,
    "longitude": 13.4370729,
    "languages": ["ar", "de", "gb", "tr"],
    "regulationSector": "akzeptiert_gesetzlich_versicherte_patient",
    "onlineBookingAvailable": true,
    "url": "https://www.doctolib.de/zahnmedizin/berlin/ziad-abdulrahim?pid=practice-797196",
    "scrapedAt": "2026-08-13T14:08:03.864Z",
    "phone": "030 6187240",
    "bio": "Liebe Patientin, lieber Patient, ich freue mich, Sie in meiner Praxis in Berlin begrüßen zu dürfen...",
    "openingHours": [
        "Mo 09:00-13:00, 14:00-18:00",
        "Tu 09:00-13:00, 14:00-18:00",
        "We 09:00-13:00, 14:00-18:00",
        "Th 09:00-13:00, 14:00-18:00",
        "Fr 09:00-13:00, 14:00-18:00",
        "Sa 09:00-13:00"
    ],
    "services": ["Implantologie", "Wurzelkanalbehandlung / Mikroskop", "Zahnersatz"]
}
```

### How to scrape Doctolib.de data

1. Open the actor and, under **Input**, set `specialty` (German, e.g.
   `zahnmedizin`, `allgemeinmedizin`, `augenheilkunde`, `frauenarzt`,
   `hautarzt`, `orthopadie`, `urologie`) and `city` (e.g. `berlin`,
   `hamburg`, `muenchen`, `koeln`, `frankfurt-am-main`).
2. Set `maxResults` to the number of providers you want. Leave
   `fetchPhoneDetails` on (default) for phone numbers and opening hours,
   or turn it off for a faster listing-only run.
3. Click **Start**. The actor loads the search listing for your
   specialty + city, calls Doctolib's internal search API directly to
   collect provider results (20 per page, paginated automatically until
   `maxResults` or the search's total is reached), then — if
   `fetchPhoneDetails` is on — visits each provider's profile page to add
   phone, bio, opening hours and services.
4. Download the results as JSON, CSV, or Excel from the **Dataset** tab,
   or pull them via the Apify API into your CRM, spreadsheet, or lead
   pipeline.

For repeat use, schedule the actor to run daily or weekly and diff the
output against your last run to catch new providers, dropped listings, or
availability changes.

### Cost estimate

This actor makes 1 search-API request per ~20 providers, plus (when
`fetchPhoneDetails` is on) 1 profile-page request per provider. At
standard Apify Pay-Per-Result pricing, that's a small, predictable cost
per result — see the actor's **Pricing** tab on the Apify Store for the
current per-result rate. Usage cost only settles once a run reports
**SUCCEEDED** — if you read the dataset mid-run or after a failed run,
the final charge may not match what you see yet.

### Limitations

- City slugs are Doctolib's own transliterated German spelling. An
  unrecognized city slug (a literal umlaut, an English city name, or a
  typo) does not error out — Doctolib silently redirects to a
  city-less, nationwide specialty page. This actor detects that case (by
  checking the resolved location against your requested city) and fails
  the run with a clear message rather than silently returning
  wrong-city data — double-check spelling if you hit that error.
- Residential proxy is recommended. Apify's shared datacenter proxy pool
  can draw Cloudflare IP-reputation blocks on profile-detail pages under
  load — the actor ships with `RESIDENTIAL` / `DE` as the default proxy
  configuration.
- Not every provider publishes a phone number or full bio — some
  practices intentionally omit contact details from their public profile.
- Specialty and city slugs must match Doctolib's own German URL
  vocabulary (the site's native routing, not free-text search).
- Doctolib's booking availability (specific appointment slots) is not
  included — this actor returns the *whether* online booking is offered,
  not live calendar slots, which change by the minute and aren't
  meaningful in a static dataset.
- Data is scraped from the public website and may change without notice.
- Respect Doctolib's terms of service and use this data responsibly —
  this actor only reads public directory pages, never registration,
  messaging, or account-management endpoints.

### Related Scrapers

- [Doctolib FR Scraper](https://apify.com/studio-amba/doctolib-fr-scraper) — same booking-directory model, France
- [Doctoralia ES Scraper](https://apify.com/studio-amba/doctoralia-es-scraper) — same booking-directory model, Spain
- [Jameda Scraper](https://apify.com/studio-amba/jameda-scraper) — German doctor review & directory platform
- [Redcare Pharmacy FR Scraper](https://apify.com/studio-amba/redcare-pharmacy-fr-scraper) — European online pharmacy data
- [Penny DE Scraper](https://apify.com/studio-amba/penny-de-scraper) — German retail data

### Need this data on a schedule, or a custom version?

We run this scraper as a managed service for businesses: scheduled runs,
deduplication, delta detection, and delivery to your inbox, Google Sheets,
or API — maintenance included. We can also build a custom version with your
exact fields and filters, or combine multiple sources into one feed.

See [studioamba.dev/services](https://studioamba.dev/services/) or email
<hello@studioamba.dev> for a free data sample.
We maintain 300+ European web scrapers and answer within one business day.

# Actor input Schema

## `specialty` (type: `string`):

Medical specialty in German, as used in the Doctolib URL slug, e.g. 'zahnmedizin' (dentist), 'allgemeinmedizin' (GP), 'augenheilkunde' (ophthalmology), 'frauenarzt' (gynecologist), 'hautarzt' (dermatologist), 'orthopadie', 'urologie', 'neurologie', 'radiologe'.

## `city` (type: `string`):

German city name. Cities with umlauts must use the ASCII-transliterated slug, e.g. 'muenchen' (not 'münchen' or 'munich'), 'koeln', 'duesseldorf'. Other examples: 'berlin', 'hamburg', 'frankfurt-am-main', 'stuttgart', 'leipzig'.

## `maxResults` (type: `integer`):

Maximum number of healthcare providers to return.

## `fetchPhoneDetails` (type: `boolean`):

When ON (default), fetches each provider's profile page to add phone number, bio, opening hours and services — one extra request per result. When OFF, only listing-page fields are returned (faster, no phone number).

## `proxyConfiguration` (type: `object`):

Proxy settings. Residential proxy is recommended for reliable profile-detail fetches — the shared Apify datacenter pool can draw Cloudflare IP-reputation blocks on Doctolib under concurrent load (same posture as the FR sibling actor).

## Actor input object example

```json
{
  "specialty": "zahnmedizin",
  "city": "berlin",
  "maxResults": 20,
  "fetchPhoneDetails": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "DE"
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "specialty": "zahnmedizin",
    "city": "berlin",
    "maxResults": 20,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "DE"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("studio-amba/doctolib-de-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "specialty": "zahnmedizin",
    "city": "berlin",
    "maxResults": 20,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "DE",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("studio-amba/doctolib-de-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "specialty": "zahnmedizin",
  "city": "berlin",
  "maxResults": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "DE"
  }
}' |
apify call studio-amba/doctolib-de-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,studio-amba/doctolib-de-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/NHhNSpK2AeQ90kQw1/builds/OLoSMpC8luFs1MIRC/openapi.json