Vitals Doctor Reviews and Ratings Scraper
Vitals hosts doctor profiles, patient-written reviews and per-doctor experience scores.
Pulling that material by hand does not scale past a few dozen pages, and running your own headless browser fleet plus proxy pool is a separate engineering project. This API accepts a Vitals URL, renders the page, rotates proxies, and returns either the rendered HTML or structured JSON. The sections below explain what comes back, which request controls change the result, how credits are consumed, and how to tell a blocked request from a rendering or selector problem.
What teams collect from Vitals
Three data groups cover most Vitals work. The first is the doctor profile: name, specialty, education, board certifications, accepted insurance and office location. The second is patient feedback: the review text itself. The third is experience scoring: wait time, bedside manner and office cleanliness, each recorded per doctor. Healthcare-directory builds, provider-research work, reputation monitoring and quality analysis all draw on one or more of these groups. Because the API returns the rendered page, anything visible on the public profile can be targeted — either with CSS selectors through extract_rules or with ai_extract_rules, which takes a natural-language spec and returns structured JSON of Vitals doctor pages with no selectors required.
Field map: profile vs review vs rating
Use this split when designing your schema, so you do not mix a profile attribute with a per-review attribute or a per-doctor score.
Request controls that change the result
The base call takes a Vitals URL. The controls below are the ones that materially change what you get back or how much it costs: render_js for JavaScript execution, stealth_proxy for CAPTCHA and block resistance, country_code for geo-targeting, and ai_extract_rules for natural-language data extraction. The descriptions here are reader guidance; the request builder and documentation carry the authoritative parameter reference.
How credits are consumed
Requests start at one credit each. Enabling JavaScript rendering raises a successful request to five credits. Premium proxies cost ten credits with JS rendering disabled, or twenty-five with it enabled. Credits are valid for one month and do not roll over. Plan tiers bundle credits with a concurrent-request ceiling; see the pricing page for the current plan table.
Telling failures apart
Three failure shapes look similar in a log but need different fixes. A block returns a challenge page or an empty body — the fix is to enable stealth_proxy. A JavaScript-not-rendered failure returns the pre-render shell with no review text — the fix is render_js=true. A selector miss returns the full page but your extract_rules produce nulls — the fix is to inspect the rendered HTML and adjust the CSS or XPath, or switch to ai_extract_rules. Checking which of the three you have before changing parameters saves credits.
A worked example
Suppose you want every review for one doctor plus that doctor's wait-time score. Send the profile URL with render_js=true so the review list is populated. Request extract_rules that target the review container and the wait-time element, or send ai_extract_rules describing both fields in plain language. The response is JSON with the review array and the score. If the review array comes back empty but the page otherwise renders, that is a selector miss, not a block — adjust the selector rather than enabling stealth_proxy, which would raise the cost from five to twenty-five credits per request.
Getting started
Create an account to receive an API key and a starting credit balance. Install the SDK for your stack — Python, Node, Go, PHP or Ruby — or send a plain GET or POST with the Vitals URL. The dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL, so you can test without writing code first. Documentation and code samples cover each language.
Compliance and scope
Public-facing pages can generally be collected, but review the target site's terms of service before deploying and avoid post-login content. The API does not collect or store personal data from scraped sites unless the user explicitly requests it. Whether a given use is lawful depends on your jurisdiction and purpose, so treat the terms review as part of your build, not an afterthought.
| Data group | Fields | Typical use |
|---|---|---|
| Doctor profile | Name, specialty, education, board certifications, accepted insurance, office location | Healthcare directories, provider research |
| Patient feedback | Review text | Quality research, reputation monitoring |
| Experience ratings | Wait time, bedside manner, office cleanliness | Per-doctor quality scoring |
Field availability depends on what each public Vitals profile displays.
| Configuration | Credits per request |
|---|---|
| Base request | 1 |
| JavaScript rendering enabled | 5 |
| Premium proxies, JS rendering disabled | 10 |
| Premium proxies, JS rendering enabled | 25 |
Credits are valid for one month and do not roll over. Plan tiers bundle credits with a concurrent-request ceiling; see the pricing page for the current plan table.
| Symptom | Likely cause | Fix |
|---|---|---|
| Challenge page or empty body | Blocked | Enable stealth_proxy |
| Pre-render shell, no review text | JavaScript not executed | Set render_js=true |
| Full page, nulls from extract_rules | Selector miss | Adjust CSS/XPath or use ai_extract_rules |
Check which failure you have before changing parameters; each change affects credit cost.
Frequently asked questions
Is scraping Vitals reviews legal?
Pages that are open to the public are generally collectable, but read the target site's terms of service before you deploy and stay away from anything behind a login. Legality also depends on your jurisdiction and purpose, so treat the terms check as part of the build.
What data can I extract from Vitals reviews?
Any content that appears on the public page is fair game. Target it with extract_rules using CSS selectors, or describe the fields in plain language with ai_extract_rules; either route returns structured JSON.
How do I start scraping Vitals reviews?
Sign up, grab your API key, and send a GET request with the target URL. We render the page, rotate proxies, and return the data. {{OWNER_FREE_CREDITS}}
Will I get blocked when scraping Vitals reviews?
Requests are routed through rotating residential proxies and a real headless browser, so they resemble ordinary traffic. If a target starts pushing back, turn on stealth_proxy for that request.
Can I scrape Vitals reviews without writing code?
Yes. Our dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL.
How do I handle JavaScript when scraping Vitals reviews?
Set render_js=true on the request. The page then runs inside a real headless browser, the JavaScript executes server-side, and you receive the HTML as it looks after rendering.