# Jameda Scraper — German Doctor Reviews & Directory Data (`studio-amba/jameda-scraper`) Actor

Scrape doctor and healthcare provider listings from jameda.de, Germany's largest doctor-review directory. Get name, specialty, address, phone, opening hours, rating and review snippets by specialty and city. No login required.

- **URL**: https://apify.com/studio-amba/jameda-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 $5.00 / 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.

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

## Jameda Scraper (jameda.de)

Scrape public doctor and healthcare-provider listings from jameda.de,
Germany's largest doctor-review and appointment-booking directory (part of
the Docplanner group, the same platform family as Doctolib). Search by
medical specialty and city and get structured provider profiles: name,
specialty, practice address, coordinates, phone, opening hours, aggregate
patient rating, review count, and individual review snippets.

### 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, along with a read on how
well-reviewed each one is. Jameda is the dominant doctor-review 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 directory
data that the doctor or clinic chose to publish on their jameda 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 — only reviews and profile
data that are already public on the page.

### Input

| Field | Type | Required | Description |
|-------|------|----------|--------------|
| `specialty` | String | No | Medical specialty in German, as used in the jameda URL, e.g. `Zahnarzt`, `Hausarzt`, `Hautarzt`, `Frauenarzt`, `Orthopäde`, `Kinderarzt`, `Psychiater`, `Urologe`, `Augenarzt`. Default: `Zahnarzt` |
| `city` | String | No | German city name, e.g. `Berlin`, `München`, `Hamburg`, `Köln`, `Frankfurt`. Default: `Berlin` |
| `maxResults` | Integer | No | Maximum number of healthcare providers to return. Default: `50` |
| `fetchDetails` | Boolean | No | When `true` (default), visits each provider's profile page for phone number, postal code, district, bio, opening hours and review snippets — one extra request per result. Set `false` for a faster, listing-only run |
| `proxyConfiguration` | Object | No | Proxy settings. jameda.de has no anti-bot wall on listing or profile pages, so the default automatic Apify proxy works |

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 | `"Gerhard Olaf Wendler"` |
| `honorific` | String | `"Dr. med. dent."` |
| `specialty` | String | `"Zahnarzt"` |
| `specialtySlug` | String | `"zahnarzt"` |
| `providerType` | String | `"INDIVIDUAL_PRACTITIONER"` or `"ORGANIZATION"` |
| `address` | String | `"Franz-Jacob-Straße 10"` |
| `city` | String | `"Berlin"` |
| `district` | String | `"Bezirk Lichtenberg"` |
| `postalCode` | String | `"10369"` |
| `country` | String | `"DE"` |
| `latitude` / `longitude` | Number | `52.5277863` / `13.4665756` |
| `phone` | String | `"030 86204681171"` |
| `bio` | String | Free-text "Über mich" profile description |
| `onlineBookingAvailable` | Boolean | `true` |
| `openingHours` | Array | `["Montag 09:00 - 19:00", "Dienstag 08:00 - 15:30", ...]` |
| `rating` | Number | `5` |
| `ratingScale` | String | `"1-5"` (worst-best; **5-star scale, not the old German 1-6 school-grade "Note" system** — jameda migrated to a 5-star scale under Docplanner) |
| `reviewCount` | Integer | `117` |
| `reviewSnippets` | Array | `[{ "text": "...", "ratingValue": 5, "date": "2026-06-16T21:57:20+02:00" }, ...]` |
| `url` | String | Full jameda.de profile URL |
| `scrapedAt` | String | ISO 8601 timestamp |

Not every field is present on every profile — `phone`, `postalCode`,
`district`, `bio`, `openingHours` and `reviewSnippets` only populate when
`fetchDetails` is on, and providers with zero reviews naturally have no
`rating`/`ratingScale`.

### Example output

```json
{
    "name": "Gerhard Olaf Wendler",
    "honorific": "Dr. med. dent.",
    "specialty": "Zahnarzt",
    "specialtySlug": "zahnarzt",
    "providerType": "INDIVIDUAL_PRACTITIONER",
    "address": "Franz-Jacob-Straße 10",
    "city": "Berlin",
    "district": "Bezirk Lichtenberg",
    "postalCode": "10369",
    "country": "DE",
    "latitude": 52.5277863,
    "longitude": 13.4665756,
    "onlineBookingAvailable": false,
    "rating": 5,
    "ratingScale": "1-5",
    "reviewCount": 5,
    "phone": "030 86204681171",
    "openingHours": [
        "Montag 09:00 - 19:00",
        "Dienstag 08:00 - 15:30",
        "Mittwoch 09:00 - 19:00",
        "Donnerstag 08:00 - 15:30",
        "Freitag 08:00 - 13:30"
    ],
    "reviewSnippets": [
        {
            "text": "Ich fühle mich stets gut aufgehoben und schätze den sachlich freundlichen Umgang in dieser Praxis.",
            "ratingValue": 5,
            "date": "2026-07-21T19:38:46+02:00"
        }
    ],
    "url": "https://www.jameda.de/gerhard-olaf-wendler/zahnarzt/berlin",
    "scrapedAt": "2026-08-11T20:07:04.226Z"
}
```

### How to scrape Jameda data

1. Open the actor and, under **Input**, set `specialty` (German, e.g.
   `Zahnarzt`, `Hausarzt`, `Hautarzt`, `Frauenarzt`, `Orthopäde`,
   `Kinderarzt`, `Psychiater`, `Urologe`) and `city` (e.g. `Berlin`,
   `München`, `Hamburg`, `Köln`).
2. Set `maxResults` to the number of providers you want. Leave
   `fetchDetails` on (default) for phone numbers, opening hours and review
   snippets, or turn it off for a faster listing-only run.
3. Click **Start**. The actor loads jameda's search listing for your
   specialty + city (server-rendered HTML, paginated automatically until
   `maxResults` or the search's results are exhausted), reads each doctor
   card's rating, review count, address and coordinates directly, then —
   if `fetchDetails` is on — visits each provider's profile page to add
   phone, opening hours, "Über mich" bio and individual review text.
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, rating changes, or
new reviews.

### Cost estimate

This actor makes 1 request per listing page (roughly 20-27 providers per
page) plus, when `fetchDetails` 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

- Not every provider publishes a phone number, bio, or opening hours on
  their profile — some practices keep their listing minimal.
- jameda's rating is a live **5-star scale** (worst = 1, best = 5), taken
  directly from the site's own schema.org markup. It is not the older
  German school-grade ("Schulnote", 1-6, lower is better) system some
  legacy German review sites still use — verify `ratingScale` on any
  record rather than assuming a fixed scale.
- Specialty and city must roughly match jameda's own German URL
  vocabulary (the site's native routing, not free-text search). A small
  set of compound specialties (e.g. "Hautarzt" → dermatology) are aliased
  to their real URL slug automatically; unusual specialty names may need
  the exact jameda slug.
- `reviewSnippets` reflects the reviews embedded in the profile page's own
  structured data, not the full review history for high-volume profiles.
- Data is scraped from the public website and may change without notice.
- Respect jameda'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
- [DocMorris Scraper](https://apify.com/studio-amba/docmorris-scraper) — German online pharmacy data
- [Handelsregister Scraper](https://apify.com/studio-amba/handelsregister-scraper) — German company registry data
- [Stellenanzeigen.de Scraper](https://apify.com/studio-amba/stellenanzeigen-de-scraper) — German job listings
- [Mobile.de Scraper](https://apify.com/studio-amba/mobile-de-scraper) — German car marketplace 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 jameda URL, e.g. 'Zahnarzt', 'Hausarzt', 'Hautarzt', 'Frauenarzt', 'Orthopäde', 'Kinderarzt', 'Psychiater', 'Urologe', 'Augenarzt'.

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

German city name, e.g. 'Berlin', 'München', 'Hamburg', 'Köln', 'Frankfurt'.

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

Maximum number of healthcare providers to return.

## `fetchDetails` (type: `boolean`):

When ON (default), fetches each provider's profile page to add phone number, postal code, district, bio, opening hours and individual review snippets — one extra request per result. When OFF, only listing-page fields are returned (faster: name, specialty, city, rating, review count, coordinates).

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

Proxy settings. jameda.de has no Cloudflare/DataDome/Akamai anti-bot on listing or profile routes (verified live) — the default automatic Apify proxy works without a residential group.

## Actor input object example

```json
{
  "specialty": "Zahnarzt",
  "city": "Berlin",
  "maxResults": 20,
  "fetchDetails": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# 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": "Zahnarzt",
    "city": "Berlin",
    "maxResults": 20,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("studio-amba/jameda-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": "Zahnarzt",
    "city": "Berlin",
    "maxResults": 20,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("studio-amba/jameda-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": "Zahnarzt",
  "city": "Berlin",
  "maxResults": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call studio-amba/jameda-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,studio-amba/jameda-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/nA9raMpSzNFTOZY8u/builds/Q51ED01n9AzHfckhY/openapi.json