# NPI Registry Scraper - Healthcare Provider Leads (`maydit/us-healthcare-providers-scraper`) Actor

Export US healthcare providers by specialty and location from the official NPPES NPI registry. Phone, fax, address per row. Smart geo match keeps every lead in your target area. CSV/JSON.

- **URL**: https://apify.com/maydit/us-healthcare-providers-scraper.md
- **Developed by:** [Brandt May](https://apify.com/maydit) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Registry Scraper - US Healthcare Provider Leads

> Pull a clean, geo-targeted list of US doctors, dentists, clinics, and organizations straight from the official CMS NPPES NPI registry - phone, fax, and address on every row.

### What it does

This NPI registry scraper turns the official CMS NPPES NPI registry into a lead-gen-ready dataset. Query US healthcare providers by specialty, taxonomy code, name, city, state, or postal code, and export a healthcare provider database to CSV or JSON in minutes. Unlike a raw NPPES NPI registry API dump that returns dozens of credentialing fields, this actor uses **smart address matching**: any provider whose address does not match your target geography is dropped, so every exported row is a real provider inside your target area. Each record includes the provider's NPI number, name, credential, primary and full specialty list, phone, fax, and mailing address - the fields sales, recruiting, and market-research teams actually use.

### Who it's for

- **Healthcare sales & lead generation** teams building targeted provider call lists
- **Medical-device and pharma reps** prospecting by specialty and territory
- **Healthcare recruiters** sourcing physicians, NPs, and specialists by location
- **Market research & analytics** teams mapping provider density by state or ZIP
- **Health-tech and SaaS** companies enriching or building a provider directory

### What you get (output)

Every row is one provider (individual or organization) with these fields:

| Field | Description |
|---|---|
| `npi` | 10-digit National Provider Identifier |
| `providerType` | Individual (NPI-1) or Organization (NPI-2) |
| `name` | Provider or organization name |
| `credential` | Credential(s), e.g. MD, DO, DDS, NP |
| `gender` | Provider gender (individuals) |
| `primarySpecialty` | Primary specialty / taxonomy description |
| `taxonomyCode` | Primary NUCC taxonomy code |
| `allSpecialties` | Full list of the provider's specialties |
| `address` | Practice / mailing street address |
| `city` | City |
| `state` | State |
| `postalCode` | ZIP / postal code |
| `phone` | Practice phone number |
| `fax` | Practice fax number |
| `soleProprietor` | Sole-proprietor flag (individuals) |
| `enumerationDate` | Date the NPI was issued |
| `npiUrl` | Direct link to the provider's NPPES record |

### Input / how to query

Filter the NPI registry by any combination of:

- **Provider type** - individual providers (NPI-1) or organizations (NPI-2)
- **Specialty / taxonomy** - target by specialty description or NUCC taxonomy code
- **Name** - provider or organization name
- **City** - narrow to a single city
- **State** - pull an entire state's providers
- **Postal code** - drill down to a specific ZIP

Set your location filters and **smart address matching** removes any provider whose registered address falls outside the target geo, so you never have to clean out-of-area rows by hand. Results export as CSV, Excel, or JSON.

### Example use cases

- **Medical-device territory list** - export every orthopedic surgeon in a set of ZIP codes with phone and address, ready for the field team.
- **Pharma specialty targeting** - pull all cardiologists in a state, filtered by taxonomy code, for a sample-drop campaign.
- **Recruiter sourcing** - build a list of nurse practitioners in a metro area, complete with practice contact details.
- **Dental / clinic outreach** - generate a dentist and clinic lead list for a region, with fax and phone for direct outreach.
- **Market sizing** - count and map provider density by state or specialty to prioritize expansion.

### Recurring use & scheduling

The NPPES NPI registry is refreshed by CMS on a regular cycle as providers are added and updated. Use Apify **Schedules** to re-run this actor weekly or monthly and keep your provider database current. Point the run at the same dataset and dedupe on the `npi` field (the NPI is unique per provider) so repeated runs surface only new or changed records instead of duplicates - ideal for ongoing lead monitoring by specialty or territory.

### FAQ

#### How do I download a list of doctors by specialty and location?

Set the specialty (or taxonomy code) filter plus a city, state, or postal code, then run the actor. It returns every matching provider with contact details, ready to export to CSV, Excel, or JSON.

#### How do I export NPI registry data to CSV or Excel?

Every run produces a structured dataset you can download as CSV, Excel, or JSON directly from the run's Storage tab, or pull via the Apify API.

#### Where can I get healthcare provider phone numbers and addresses for sales?

This actor sources them from the official CMS NPPES NPI registry. Each row includes the provider's registered practice `phone`, `fax`, and mailing `address`, so your list is contact-ready.

#### Is there a free NPPES NPI registry API without a key?

The underlying CMS NPPES data is public and this actor reads it without any API key on your part. You run it on Apify and get a clean, filtered dataset instead of raw API pagination.

#### How do I build a physician mailing list by state?

Filter by state (optionally narrowing by specialty or ZIP), run the actor, and export the results. Each row carries the provider's name, credential, and full mailing address for direct mail.

#### How can I find providers by taxonomy code or specialty in a specific ZIP?

Combine the taxonomy/specialty filter with a postal code. Smart address matching drops any provider outside that ZIP, so the export contains only in-area providers.

#### How do I get NPI data for individual vs organization providers?

Use the provider-type filter: NPI-1 for individual providers, NPI-2 for organizations. The `providerType` field in the output labels each row so you can split or segment them.

#### Is scraping the CMS NPI registry legal?

The NPPES NPI registry is published by CMS as public data specifically for lookups and downloads. This actor reads that public information; as always, ensure your outreach complies with applicable marketing and privacy regulations.

#### How often is the NPPES NPI registry updated?

CMS updates NPPES regularly as providers enroll and revise their records. Schedule this actor to re-run on your preferred cadence to keep your dataset in sync.

### Data source & notes

- **Source:** Official CMS NPPES NPI Registry (National Plan and Provider Enumeration System) - public US government data, no API key required.
- **Coverage:** US individual providers (NPI-1) and organizations (NPI-2).
- **Fields:** Only the fields listed in the output table above are returned - this actor deliberately delivers the lead-relevant subset rather than every raw credentialing field.
- **Geo accuracy:** Smart address matching keeps results inside your specified location, so no manual cleanup of out-of-area rows.
- **Compliance:** Data is public, but you are responsible for using it in line with applicable marketing, calling, and privacy laws.

### Related actors

Part of a set of US public-records tools that work well together:

- [FDA Adverse Events Scraper](https://apify.com/maydit/us-fda-adverse-events-scraper) - device and drug safety reports for the same market
- [FDA Recalls Scraper](https://apify.com/maydit/us-fda-recalls-scraper) - recall monitoring for medical products

See all fifteen at [apify.com/maydit](https://apify.com/maydit).

### Found this useful?

If this actor saved you time, a short review on the Apify Store genuinely helps. Reviews are how the next person decides whether a tool is worth trying.

Something broken, missing a field, or a source you want covered? Open an issue on the **Issues** tab and it will get looked at - that is the fastest route to getting it changed.

# Actor input Schema

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

Individual = clinicians (doctors, dentists, nurses, therapists). Organization = clinics, hospitals, group practices, pharmacies.

## `specialty` (type: `string`):

Provider specialty / taxonomy description, e.g. 'Cardiovascular Disease', 'Dentist', 'Physical Therapist', 'Dermatology', 'Pharmacy'. Leave empty for all.

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

Two-letter US state code, e.g. 'CA', 'TX', 'NY'. Strongly recommended to narrow results.

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

City name to narrow results, e.g. 'San Diego'.

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

ZIP code (or ZIP prefix) to narrow results.

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

Filter individuals by first name (supports partial). Leave empty for all.

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

Filter individuals by last name (supports partial). Leave empty for all.

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

Filter organizations by name (supports partial). Leave empty for all.

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

Upper bound on providers returned per run. Note: the NPI Registry API returns at most 1,200 results per unique query — narrow by specialty + state + city to get everyone in a niche.

## Actor input object example

```json
{
  "providerType": "individual",
  "specialty": "Physical Therapist",
  "state": "CA",
  "maxResults": 500
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("maydit/us-healthcare-providers-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("maydit/us-healthcare-providers-scraper").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 '{}' |
apify call maydit/us-healthcare-providers-scraper --silent --output-dataset

```

## MCP server setup

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

```

## OpenAPI specification

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