# NPI Healthcare Provider Leads Scraper - Phone + Lead Scores (`flash_scraper/npi-healthcare-leads`) Actor

Scrape the official CMS NPPES NPI registry — every licensed US healthcare provider — by specialty, state, city or name. Get name, NPI, phone, fax, address, license, Medicare/Medicaid IDs + a 0-100 lead score per provider. Filter active / with-phone, dedupe. Export CSV, JSON, Excel. No API key.

- **URL**: https://apify.com/flash\_scraper/npi-healthcare-leads.md
- **Developed by:** [Flash Scrape](https://apify.com/flash_scraper) (community)
- **Categories:** Lead generation, Automation, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 results

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

## NPI Healthcare Provider Scraper - Leads by Specialty

**This NPI scraper turns the official CMS NPPES registry into clean, contactable healthcare-provider leads** — every licensed US doctor, dentist, therapist, pharmacy, clinic, and facility. Search by **specialty, state, city, ZIP, or name** and get one flat row per provider: name + credential, specialty, NPI, status, **phone**, fax, full practice address, and license. Filter to active / with-phone, dedupe, and export to CSV, JSON, or Excel.

Built for **medical-device & pharma sales, healthcare recruiters, billing/RCM & MSO services, insurance, and B2B marketers** who need callable provider leads by specialty + location — straight from the authoritative government source, no API key.

***

### Why this beats a generic "doctor list"

- **Authoritative + current** — the official CMS NPPES NPI Registry (every US provider must enroll), not a stale scraped list.
- **Phone on most records** — the practice-location phone, so leads are callable out of the box.
- **0-100 `lead_score`** — a contactability score (phone, active status, license, payer IDs, multiple locations, recency) so you can work the best leads first.
- **Decoded payer IDs** — `medicare_id`, `medicaid_id`, and other identifiers pulled out of the registry — a feature paid provider databases charge for, free here.
- **Every practice location** — a `practice_locations` array (address + phone per site) and a `location_count`, not just the primary address rivals stop at — map a provider's whole footprint.
- **Specialty-precise** — search by taxonomy ("physical therapist", "dermatology", "pharmacy") instead of fuzzy keywords, with `taxonomy_group` + `taxonomy_code` and all secondary specialties.
- **Direct/FHIR `secure_endpoints`** surfaced for health-IT and interoperability outreach.
- **Clean flat rows** — NPPES returns deeply nested JSON; this flattens it to a spreadsheet, with the primary specialty and practice address extracted for you.
- **No API key, no anti-bot, no proxies** — public government data.

***

### How to use it

1. Enter a **specialty** (taxonomy) and/or a **state / city / ZIP** — or a specific provider/organization name.
2. Choose provider type (individuals, organizations, or both) and optional filters (active only, has-phone).
3. Run → get a clean, deduped provider list.

#### Input

| Field | Type | Description |
|---|---|---|
| `taxonomy` | string | Specialty, e.g. `dentist`, `physical therapist`, `pharmacy`. |
| `state` | string | Two-letter state code (e.g. `CA`). |
| `city` | string | City (optional). |
| `postalCode` | string | ZIP (optional). |
| `providerType` | string | All / Individuals / Organizations. |
| `firstName` / `lastName` / `organizationName` | string | Name search (optional; wildcards OK). |
| `maxItems` | integer | Max providers (NPPES caps any single search at 1,200). |
| `onlyActive` | boolean | Keep only active-status NPIs. Default `true`. |
| `onlyWithPhone` | boolean | Keep only providers with a phone. |

> **Tip:** NPPES caps any single query at 1,200 results. For a whole specialty nationwide, run it once **per state** (and per city for dense specialties) to get full coverage.

**Example input:**

```json
{
  "taxonomy": "dentist",
  "state": "CA",
  "providerType": "individual",
  "onlyWithPhone": true,
  "maxItems": 500
}
```

#### JSON output sample

```json
{
  "npi": "1234567890",
  "lead_score": 90,
  "provider_type": "Individual",
  "name": "Jane Smith",
  "credential": "DDS",
  "primary_specialty": "Dentist, General Practice",
  "taxonomy_group": null,
  "taxonomy_code": "1223G0001X",
  "all_specialties": ["Dentist, General Practice", "Dentist, Orthodontics"],
  "status": "Active",
  "phone": "415-555-0123",
  "fax": "415-555-0124",
  "address": "123 Market St, Suite 200, San Francisco, CA, 94103",
  "city": "San Francisco",
  "state": "CA",
  "postal_code": "94103",
  "practice_locations": [
    { "address": "456 Mission St, San Francisco, CA, 94105", "city": "San Francisco", "state": "CA", "phone": "415-555-0150" }
  ],
  "location_count": 2,
  "license": "12345",
  "license_state": "CA",
  "medicare_id": "1A2B3C4D5E",
  "medicaid_id": "02770029",
  "other_ids": [{ "type": "MEDICAID", "id": "02770029", "state": "CA" }],
  "secure_endpoints": [],
  "other_names": [],
  "sole_proprietor": "YES",
  "enumeration_date": "2008-05-23",
  "last_updated": "2024-02-10",
  "has_phone": true,
  "has_payer_id": true
}
```

Results render as a clean, sortable table on the Output tab and export to CSV, JSON, or Excel.

**How often each column is actually filled.** NPPES is a registration file, not a contact database, so some columns are thin — the sample above shows a fully-populated provider and is a best case, not a typical row. Measured over a 150-provider California sample: `phone` **100%**, `sole_proprietor` **27%**, `credential` (DDS, MD, …) **24%**, `medicare_id` **6%**, `medicaid_id` **2%**. There is **no email column at all** — the federal registry simply does not publish provider email addresses, so pair this with an email-pattern or verification Actor if you need one. Sparse columns are `null` rather than absent, so filtering on them is safe.

#### Example output

A real sample from a live run:

| npi | name | primary\_specialty | city | state | phone |
|---|---|---|---|---|---|
| 1760813802 | 101 DENTAL GROUP | Dentist, General Practice | CANOGA PARK | CA | 818-999-9900 |
| 1730535774 | 1012 GROUP, INC | Dentist, General Practice | SAN MATEO | CA | 650-458-3727 |
| 1649406133 | 1692 TULLY DENTISTRY | Dentist | SAN JOSE | CA | 408-279-2114 |
| 1013799931 | 1706 SAPANA KOTHARY DDS INC | Clinic/Center, Multi-Specialty | SAN JOSE | CA | 408-478-9081 |

***

### Use cases

- **Medical-device & pharma sales** — build a calling list of every cardiologist / dentist / PT in a territory.
- **Healthcare recruiting** — source providers by specialty + location.
- **Billing / RCM / MSO outreach** — target independent practices (sole proprietors) by specialty.
- **Insurance & networks** — verify and enrich provider rosters by NPI.
- **Market sizing** — count providers by specialty across states.

***

### Use with AI agents & automation

Run from the Apify **MCP** server so AI agents (Claude, ChatGPT, Cursor) can pull provider leads as a tool call, schedule runs via **Make**, **n8n**, or **Zapier** to feed a CRM, or sync the dataset to **Google Sheets**. Clean flat JSON drops into sales pipelines with no glue code.

***

### Pricing

**Pay-per-event — charged per provider lead delivered.** Source data is the free public NPPES API (no proxy or third-party cost). See the Apify Store page for the current per-result price.

***

### FAQ

**Where does the data come from?** The official **NPPES NPI Registry** maintained by CMS (the U.S. Centers for Medicare & Medicaid Services) — public, authoritative data every US provider must enroll in.

**Do I need an API key?** No. It works key-free.

**Is there an email field?** NPPES does not publish provider emails — it exposes the practice **phone**, fax, and address. Pair with a website-email finder if you need email.

**Why only 1,200 per search?** That's NPPES's own cap per query. Run per-state (and per-city for big specialties) to cover an entire specialty.

**Is this legal?** NPPES data is **public US government data** released for exactly this kind of use. Follow applicable calling/marketing laws (TCPA, Do-Not-Call) when you contact providers.

**Can I export to CSV or Google Sheets?** Yes — CSV, JSON, or Excel from the Output tab, or sync to Google Sheets via Make, n8n, or Zapier.

***

### Other Flash Scrape scrapers

- [Google Maps Leads Scraper](https://apify.com/flash_scraper/google-maps-leads-opener) — local business leads
- [Yelp Leads Scraper](https://apify.com/flash_scraper/yelp-leads-scraper) — business leads + email
- [FDA Recall Scraper](https://apify.com/flash_scraper/fda-recall-scraper) — drug/device/food recalls
- [Trustpilot Reviews Scraper](https://apify.com/flash_scraper/trustpilot-reviews-scraper) — company reviews
- [Indeed Jobs Scraper](https://apify.com/flash_scraper/indeed-jobs-scraper) — job listings

# Actor input Schema

## `taxonomy` (type: `string`):

Provider specialty to search, e.g. 'dentist', 'physical therapist', 'chiropractor', 'family medicine', 'pharmacy'.

## `state` (type: `string`):

Two-letter US state code, e.g. 'CA', 'TX', 'NY'.

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

City to search within, e.g. 'Houston' or 'Miami'. Combine with State for more precise results.

## `postalCode` (type: `string`):

ZIP code (optional). Supports a 5-digit code.

## `providerType` (type: `string`):

Individual practitioners, organizations, or both.

## `firstName` (type: `string`):

Individual provider first name (optional; supports wildcards like 'Jo\*').

## `lastName` (type: `string`):

Individual provider last name (optional; supports wildcards).

## `organizationName` (type: `string`):

Organization/facility name (optional; supports wildcards).

## `maxItems` (type: `integer`):

Maximum providers to return (NPPES caps any single search at 1,200 — narrow by specialty + state + city for full coverage).

## `onlyActive` (type: `boolean`):

Keep only providers with an active NPI status.

## `onlyWithPhone` (type: `boolean`):

Drop providers with no practice phone number (best for cold calling).

## Actor input object example

```json
{
  "taxonomy": "dentist",
  "state": "CA",
  "providerType": "all",
  "maxItems": 100,
  "onlyActive": true,
  "onlyWithPhone": false
}
```

# 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 = {
    "taxonomy": "dentist",
    "state": "CA"
};

// Run the Actor and wait for it to finish
const run = await client.actor("flash_scraper/npi-healthcare-leads").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 = {
    "taxonomy": "dentist",
    "state": "CA",
}

# Run the Actor and wait for it to finish
run = client.actor("flash_scraper/npi-healthcare-leads").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "taxonomy": "dentist",
  "state": "CA"
}' |
apify call flash_scraper/npi-healthcare-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=flash_scraper/npi-healthcare-leads",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

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