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

{
    "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 — same booking-directory model, France
• DocMorris Scraper — German online pharmacy data
• Handelsregister Scraper — German company registry data
• Stellenanzeigen.de Scraper — German job listings
• 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 or email hello@studioamba.dev for a free data sample. We maintain 300+ European web scrapers and answer within one business day.