# Healthcare Provider Leads Scraper (`talcoe/npi-provider-leads`) Actor

Get doctors, dentists and clinics from the official NPI Registry, filtered by specialty, city, state, ZIP and provider type, with phone, address and license, priced per result.

- **URL**: https://apify.com/talcoe/npi-provider-leads.md
- **Developed by:** [M Usama](https://apify.com/talcoe) (community)
- **Categories:** Lead generation, Business
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 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/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### What does Healthcare Provider Leads Scraper (NPI Registry) do?

It pulls doctors, dentists, clinics and other healthcare providers from the official US NPI Registry and returns clean, flat records: name, specialty, practice phone, practice address, license number, credential and the NPI number. Filter by specialty, city, state, ZIP code and provider type (individual or organization). Pricing is per result, and `maxResults` caps every run.

### Data source

The public NPPES NPI Registry API run by CMS (npiregistry.cms.hhs.gov), which is updated by the registry daily.

### Why use it?

- Build local lead lists for dental, medical, chiropractic, physical therapy or any other specialty by city or ZIP code.
- Find clinics and group practices (organization records) with the authorized official and their title.
- Verify that a provider exists, is active, and holds a license in a given state.
- Refresh a CRM or territory map without a paid provider database.

### How to use it

1. Open the Actor and set the filters.
2. Click Start. Download results as JSON, CSV or Excel, or read them through the API.
3. Add a Schedule and an Integration (Slack, Google Sheets, webhook) to get new records automatically.

### Input

| Field | Description |
|---|---|
| `taxonomyDescription` | Specialty, for example `Dentist`, `Cardiology`, `Chiropractor`. Matches the start of the taxonomy name. |
| `city` | City of the practice location. |
| `state` | Two letter state code, for example `TX`. |
| `postalCode` | Optional 5 digit ZIP code. |
| `enumerationType` | `ANY`, `NPI-1` (individuals) or `NPI-2` (organizations). |
| `maxResults` | Hard stop for the run. You are billed per result, so this caps the cost. |
| `proxyConfiguration` | Apify proxy is recommended for larger runs. |

At least one of specialty, city or ZIP code is required, because the registry does not accept a state on its own.

Example input:

```json
{ "taxonomyDescription": "Dentist", "city": "Austin", "state": "TX", "enumerationType": "ANY", "maxResults": 50 }
```

### Output

Every record has the same shape:

```json
{
    "id": "1881105682",
    "npi": "1881105682",
    "name": "Dr. Sarah Khalid Abdat",
    "entityType": "individual",
    "credential": "B.D.S, M.S",
    "primarySpecialty": "Dentist, Endodontics",
    "taxonomyCode": "1223E0200X",
    "phone": "254-699-7855",
    "street": "4400-1 E Central Texas Expy Ste B",
    "city": "Killeen",
    "state": "TX",
    "postalCode": "76543-7309",
    "licenseNumber": "33568",
    "licenseState": "TX",
    "otherSpecialties": [],
    "authorizedOfficial": null,
    "status": "active",
    "enumerationDate": "2017-10-19",
    "lastUpdated": "2018-03-17",
    "url": "https://npiregistry.cms.hhs.gov/provider-view/1881105682"
}
```

| Field | Meaning |
|---|---|
| `id` / `npi` | NPI number, stable key, safe for deduplication between runs |
| `entityType` | `individual` or `organization` |
| `primarySpecialty` | Primary taxonomy description |
| `phone`, `fax` | Practice location contact numbers, when listed |
| `street`, `city`, `state`, `postalCode` | Practice location address |
| `licenseNumber`, `licenseState` | License of the primary taxonomy |
| `otherSpecialties` | Additional taxonomies |
| `authorizedOfficial` | Name, title and phone for organizations |
| `mailingAddress` | Mailing address, when different |
| `lastUpdated` | Last registry update, ISO date |

### Pricing

Pay per event: a small fee when a run starts, then a fixed price per result returned. You only pay for records that pass your filters. Set `maxResults` to cap any run.

### Limitations

- The registry returns at most 1,200 records per search. For large markets, run one search per city or ZIP code.
- Email addresses are not part of the registry. Phone numbers are missing for some providers.
- Data is only as current as what providers file with CMS.

### FAQ

**Is this legal?** The Actor reads listings the site publishes for any visitor without a login and stores only business information published for that purpose. You are responsible for how you use the data.

**Something is missing or broken?** Open an issue in the Issues tab; response time is usually under a day.

# Actor input Schema

## `taxonomyDescription` (type: `string`):

Provider specialty or taxonomy, for example Dentist, Cardiology, Chiropractor, Pediatrics, Physical Therapist. Matches the start of the taxonomy name. Leave empty to search by location only.

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

City of the practice location, for example Austin.

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

Two letter US state or territory code, for example TX. Use together with a specialty or city.

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

Optional 5 digit ZIP code to narrow the search, for example 78701.

## `enumerationType` (type: `string`):

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

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

Hard stop for the run. You are billed per result, so this caps the cost. The registry returns at most 1,200 records per search, so split bigger markets by city or ZIP code.

## `proxyConfiguration` (type: `object`):

Apify proxy is recommended for larger runs.

## Actor input object example

```json
{
  "taxonomyDescription": "Dentist",
  "city": "Austin",
  "state": "TX",
  "enumerationType": "ANY",
  "maxResults": 50,
  "proxyConfiguration": {
    "useApifyProxy": 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 = {
    "taxonomyDescription": "Dentist",
    "city": "Austin",
    "state": "TX",
    "enumerationType": "ANY",
    "maxResults": 50,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("talcoe/npi-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 = {
    "taxonomyDescription": "Dentist",
    "city": "Austin",
    "state": "TX",
    "enumerationType": "ANY",
    "maxResults": 50,
    "proxyConfiguration": { "useApifyProxy": False },
}

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

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

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

```

## CLI example

```bash
echo '{
  "taxonomyDescription": "Dentist",
  "city": "Austin",
  "state": "TX",
  "enumerationType": "ANY",
  "maxResults": 50,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call talcoe/npi-provider-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,talcoe/npi-provider-leads"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

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