Doctolib Provider Directory Scraping API
Collect practitioner profiles, appointment availability and patient ratings from Doctolib through a single API call, with browser rendering, proxy handling and structured extraction managed for you.
Each request returns fresh page data, so you can build directory, comparison and availability-monitoring pipelines without running your own scraping infrastructure.
What you can pull from Doctolib
Most Doctolib collection work falls into three buckets. Availability slots support lead generation, competitor analysis and positioning work. Testimonials help with credibility, product feedback and targeted marketing. Practitioner profiles reveal market trends, competitor offerings and partnership candidates. A practitioner page can typically provide name, specialty, address, languages spoken, accepted insurance, open appointment slots and patient ratings in one response.
How it works
Step 1: Create an account to receive an API key and an introductory credit allowance, confirmed by the owner. Step 2: Install the SDK for your stack — Python, Node, Go, PHP or Ruby are listed — so each scrape is a single function call without managing proxy rotation or a headless browser yourself. Step 3: Send the Doctolib URL together with your API key; the page is rendered in a real browser, the IP is rotated, and the response is returned for parsing. Step 4: Add advanced parameters only when needed: render_js for JavaScript, stealth_proxy for CAPTCHA challenges, country_code for geo-targeting, and ai_extract_rules for natural-language extraction. A practical checklist before a production run: confirm the exact URL type (provider or plan page), decide whether rendered HTML or parsed JSON is needed, choose extract_rules versus ai_extract_rules, set country_code if content varies by location, and budget credits according to the options table below.
Rendering, extraction and automation options
Beyond raw HTML, the API supports AI-driven selectors for precise extraction, full-page screenshots, JavaScript scenarios that click, scroll and wait for dynamic content, and clean Markdown or plain-text output for analysis. No-code automation through n8n is also described for doctor and appointment-data monitoring workflows. Proxy rotation and headless-browser rendering are used to mimic real browsing behaviour and reduce IP-based blocking, and the platform is described as scaling across many browsers and rotating proxies during traffic spikes.
Compliance, documentation and plans
The service states that it does not collect or store personal data from scraped sites unless a user explicitly requests it. Code examples are listed for Java, Python, Go, PHP, cURL and JavaScript, alongside documentation and a knowledge base. Plan pricing, credit allowances and support inclusions vary by tier and are held as owner-confirmed inputs rather than asserted here.
| Option | Use it when | Listed credit cost |
|---|---|---|
| Base request | Static page content is sufficient | From 1 credit |
| render_js | Page needs JavaScript executed | 5 credits |
| Premium proxies without JS | IP rotation needed, no rendering | 10 credits |
| premium_proxy with JS | Rendering plus premium routing | 25 credits |
| stealth_proxy | CAPTCHA / anti-bot challenge expected | 75 credits |
Credit costs as listed in the captured material; confirm current costs before publication.
| Field / parameter | Purpose |
|---|---|
| render_js | Execute JavaScript in a headless browser |
| country_code | Route through an IP in a specific country |
| stealth_proxy | Handle CAPTCHA challenges |
| extract_rules | Map CSS selectors to JSON field names |
| ai_extract_rules | Natural-language extraction specification |
Parameter names preserved exactly as listed; do not rename.
Frequently asked questions
How do I handle JavaScript when scraping Doctolib?
Set render_js=true. The page is executed in a headless browser and the HTML returned is the version after scripts have run, rather than the initial markup.
Can I scrape Doctolib from a specific country?
Yes. Supply country_code to route the request through an IP in the chosen country, which helps when the visible content differs by location.
What's the rate limit for scraping Doctolib?
Limits are applied per plan as concurrency limits, not as a separate per-target rate limit. If Doctolib throttles aggressive patterns, spacing requests or using multiple sessions can help.
How do I get structured JSON from Doctolib?
Use extract_rules to map CSS selectors to field names, or ai_extract_rules with a plain-language specification. Either approach returns parsed JSON.
Which programming languages can I use to scrape Doctolib?
Any common stack works: SDKs are listed for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL is also supported.
How much does it cost to scrape Doctolib?
Credit use depends on the options enabled: JavaScript rendering is listed at 5 credits, premium_proxy with JavaScript at 25 credits, and stealth_proxy at 75 credits. Plan prices and any introductory credit allowance must be confirmed by the owner before publication — see the owner inputs for this page.