# Healthcare Provider Leads Scraper: NPI Contacts by Specialty (`scrapemint/healthcare-provider-leads`) Actor

US healthcare provider leads from the official NPI registry: search by specialty, state, city, or ZIP and get one row per provider with practice phone, address, license, and for organizations the decision maker's name, title, and phone. Keyless official API, no browser. Pay per provider.

- **URL**: https://apify.com/scrapemint/healthcare-provider-leads.md
- **Developed by:** [Ken M](https://apify.com/scrapemint) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 provider lead rows

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

## Healthcare Provider Leads Scraper: NPI Contacts by Specialty

Build US healthcare provider lead lists from the official NPI registry (CMS NPPES), the public record every practicing provider and healthcare organization must be in. Search by specialty, state, city, or ZIP and get one JSON row per provider with the practice phone number, address, specialty taxonomy, and license, and for organizations the authorized official: the decision maker's name, title, and phone. Keyless official government API: no login, no browser, no per-seat directory subscription.

Built for dental and medical software vendors, device and supply reps, healthcare recruiters and staffing agencies, insurance and billing services, and local marketers selling to practices.

### What you get

One row per provider, with:

- `npi`, `providerType` (individual or organization), `name`, `credential`
- `specialty`, `taxonomyCode`, `licenseNumber`, `licenseState`
- `phone`, `fax`, `address1`, `address2`, `city`, `state`, `postalCode`
- `authorizedOfficialName`, `authorizedOfficialTitle`, `authorizedOfficialPhone` (organizations: the practice's decision maker)
- `status`, `enumerationDate`, `lastUpdated`, `profileUrl`

`enumerationDate` tells you how new the provider is: recently enumerated NPIs are new practices and new graduates, the leads with no incumbent vendors yet.

### Input

- `specialties` (matched against taxonomy descriptions, e.g. dentist, chiropractor, physical therapy, family medicine, pharmacy)
- `states` / `cities` / `postalCodes` (a trailing `*` on a ZIP matches the prefix, e.g. `787*` for all of Austin)
- `providerType` (both, individuals only, or organizations only — organizations carry the decision-maker fields)
- `maxProviders` (default 50, up to 2000)
- `dedupe` (skip previously returned NPIs; built for scheduled prospecting)

### Example input

```json
{
  "specialties": ["dentist"],
  "states": ["TX"],
  "providerType": "organization",
  "maxProviders": 200
}
```

### Example output

```json
{
  "npi": "1154494250",
  "providerType": "organization",
  "name": "360 DENTAL CARE P.A.",
  "specialty": "Dentist, General Practice",
  "taxonomyCode": "1223G0001X",
  "phone": "512-327-3631",
  "address1": "3300 BEE CAVES RD STE 305",
  "city": "AUSTIN",
  "state": "TX",
  "postalCode": "787468106",
  "authorizedOfficialName": "JANE DOE",
  "authorizedOfficialTitle": "OWNER",
  "authorizedOfficialPhone": "512-327-3631",
  "enumerationDate": "2009-02-01",
  "profileUrl": "https://npiregistry.cms.hhs.gov/provider-view/1154494250"
}
```

### Uses

- Call and mail lists for anyone selling software, devices, supplies, or services to practices, segmented by specialty and geography
- Organizations mode: skip gatekeepers and get the authorized official's name and title per practice
- Healthcare recruiters: every licensed provider in a specialty and metro, with license numbers
- Scheduled prospecting with `dedupe` on: only never-seen providers each run
- Chain practice names into the Website Contact Scraper for emails once you have the list

### Pricing

Pay per provider row. Providers without any phone number are free rows, and searches that match nothing cost nothing. The first 2 rows of every run are free so you can validate output before you scale up.

### Notes

- Data comes from the official CMS NPPES NPI registry API and reflects what providers filed; addresses are practice locations, and phone coverage is near universal.
- A state on its own is not accepted by the registry; combine it with a specialty, city, or ZIP.
- Wide searches fan out: each specialty x location combo pages through the registry 200 rows at a time.

# Actor input Schema

## `specialties` (type: `array`):

Specialty keywords matched against NPI taxonomy descriptions, e.g. dentist, chiropractor, physical therapy, family medicine, pharmacy.

## `states` (type: `array`):

Two-letter US state codes, e.g. TX, CA, NY. Empty = all states.

## `cities` (type: `array`):

City names, combined with each state if states are set.

## `postalCodes` (type: `array`):

5-digit ZIPs; a trailing \* matches a prefix, e.g. 787\* for all of Austin. Used instead of cities/states when set.

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

Individual providers (doctors, dentists), organizations (practices, clinics, pharmacies), or both.

## `maxProviders` (type: `integer`):

Cap on provider rows returned. Controls total cost.

## `dedupe` (type: `boolean`):

Remember returned NPIs across runs and skip them. Turn on for scheduled prospecting.

## Actor input object example

```json
{
  "specialties": [
    "dentist"
  ],
  "states": [
    "TX"
  ],
  "cities": [],
  "postalCodes": [],
  "providerType": "all",
  "maxProviders": 50,
  "dedupe": false
}
```

# 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 = {
    "specialties": [
        "dentist"
    ],
    "states": [
        "TX"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapemint/healthcare-provider-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 = {
    "specialties": ["dentist"],
    "states": ["TX"],
}

# Run the Actor and wait for it to finish
run = client.actor("scrapemint/healthcare-provider-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 '{
  "specialties": [
    "dentist"
  ],
  "states": [
    "TX"
  ]
}' |
apify call scrapemint/healthcare-provider-leads --silent --output-dataset

```

## MCP server setup

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

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/Ga3td1dkMNapa144Y/builds/R1j6MCpiROyRt8Uws/openapi.json