# Healthcare Provider Leads — NPI Registry Search & Monitor (`shrid5/npi-provider-leads`) Actor

Search 8M+ US healthcare providers in the NPI registry by specialty, location, and type. Get phones, addresses, and licenses. Monitor mode delivers newly registered providers on scheduled runs.

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

## Pricing

from $1.00 / 1,000 provider 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?

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 — NPI Registry Search & Monitor

Unofficial. Not affiliated with, endorsed by, or sponsored by CMS or the NPPES NPI Registry.

Search 8 million+ US healthcare providers in the official CMS NPI registry by specialty, location, and provider type. Get phone numbers, practice addresses, licenses, and enumeration dates — then turn on monitor mode to receive newly registered providers on every scheduled run. Built for medical device sales, pharma field teams, healthcare recruiting, and local patient-acquisition agencies.

### What you get

Each dataset item is one provider:

```json
{
  "npi": "1932307261",
  "providerType": "individual",
  "name": "WILLIAM ABIDE, M.D.",
  "firstName": "WILLIAM",
  "lastName": "ABIDE",
  "credential": "M.D.",
  "organizationName": null,
  "primarySpecialty": "Internal Medicine, Cardiovascular Disease",
  "taxonomyCode": "207RC0000X",
  "licenseNumber": "P5252",
  "licenseState": "TX",
  "address": "1330 WONDER WORLD DR",
  "city": "SAN MARCOS",
  "state": "TX",
  "zip": "786667566",
  "phone": "512-396-5603",
  "fax": "512-396-5623",
  "mailingAddress": {
    "address": "7800 SHOAL CREEK BLVD",
    "city": "AUSTIN",
    "state": "TX",
    "zip": "787571098",
    "phone": "512-206-4341",
    "fax": "512-407-1947"
  },
  "enumerationDate": "2007-07-09",
  "lastUpdated": "2022-01-21",
  "status": "A"
}
```

### How to use

1. Open this Actor in Apify Console and fill in the input form. **State is required.** Add a city, ZIP, and/or specialty so the NPI registry can search (a state-only query is automatically split into ZIP-prefix shards).
2. Set **Maximum providers** to cap cost. Leave **Provider type** on “Both” unless you only want individuals or organizations.
3. Click **Start**. Export the dataset as JSON, CSV, or Excel when the run finishes.

Worked example input (cardiovascular specialty providers matching Austin, TX — up to 5 rows):

```json
{
  "state": "TX",
  "city": "Austin",
  "specialty": "Cardiovascular",
  "maxResults": 5
}
```

`Cardiovascular` is sent to the registry as `Cardiovascular*` unless you already included a `*` wildcard (prefix match on the taxonomy description). Prefer `Cardiovascular` over `Cardiology` when searching Austin — NPPES prefix-match means `Cardiology*` misses rows tagged “Cardiovascular Disease”.

### Pricing

| Event | Price | When you are charged |
| --- | --- | --- |
| Actor start (`apify-actor-start`) | $0.00005 | Once per run (automatic; first 5 seconds of compute are covered) |
| Provider record (`provider-result`) | $0.001 | Each unique provider written to the dataset |

Scraping 5,000 providers costs **$5.00 + $0.00005 start fee**.

You are not charged `provider-result` when a run returns zero providers.

### Monitor mode / scheduling

Turn on **Monitor mode (new providers only)** and create a daily or weekly schedule in Apify Console (Actor → Schedules).

- The actor stores a cursor (the latest `enumerationDate` it emitted) in a named key-value store, keyed by your input filters, so two schedules with different specialties do not overwrite each other.
- **First monitor run** (no cursor yet): emits every provider that matches your filters, then saves the cursor.
- **Later runs**: emit only providers with `enumerationDate` strictly after that cursor — a fresh-leads feed of newly registered NPIs.
- The cursor is the maximum date emitted, not “now”, so clock skew cannot drop records.

### Integrations

- **API:** Call actor `shrid5/npi-provider-leads` (or `https://apify.com/shrid5/npi-provider-leads`) with the Apify REST API or JS/Python client. Pass the same JSON input as the Console form.
- **MCP:** Apify Actors are callable from MCP/AI-agent clients, so an assistant can search providers and return structured leads.
- **Webhooks:** Fire a webhook on run success to notify Slack, a CRM, or your own endpoint.
- **Make / Zapier / n8n:** Use the official Apify apps to send new provider rows into Google Sheets, HubSpot, Salesforce, or email.

### FAQ

**How do I get a list of cardiologists in Texas?**
Set State to TX and Specialty to `Cardiovascular` (a `*` wildcard is added for you, so the registry sees `Cardiovascular*`). Prefer `Cardiovascular` over `Cardiology` — NPPES prefix-match means `Cardiology*` misses rows tagged “Cardiovascular Disease”. Add a city such as Austin or a ZIP prefix such as `787*` to narrow the list. Increase Maximum providers if you need more than the default 1,000.

**Does this include phone numbers and addresses?**
Yes. Practice (LOCATION) address, city, state, ZIP, phone, and fax are mapped onto each row. The mailing address is included as a nested object when the registry has one.

**What is NPI-1 vs NPI-2?**
NPI-1 is an individual (physician, NP, therapist). NPI-2 is an organization (group, clinic, hospital). Use Provider type to filter, or leave it on Both.

**Why did a huge state-wide search return more than 1,200 rows?**
The NPI registry caps any single query at 1,200 rows. This actor automatically shards by ZIP prefix (`0*`–`9*`, then `70*`, `71*`, …) and dedupes by NPI so large states still complete.

**Is using NPI registry data legal?**
This actor reads the official public CMS NPPES API only. You are responsible for how you use the leads (TCPA, GDPR/CCPA, and your own compliance policies). We do not scrape login-walled pages or sell skip-traced personal data.

**How does billing work if I hit my spending cap?**
The actor charges `provider-result` after each batch of up to 100 providers. If your max-total-charge limit is reached it logs `Charge limit reached, stopping gracefully`, saves the monitor cursor, and stops without throwing.

### Support

Maintained by [Shrithan](https://apify.com/shrid5). Open an issue on this Actor or email shrithanofficial@gmail.com.

# Actor input Schema

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

US state or DC where the provider practices. This is required. The official NPI registry needs a state plus at least one extra filter (city, ZIP, or specialty).

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

City name to narrow results (for example, Austin). Leave blank to search the whole state (the actor will automatically split the search by ZIP prefix).

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

US ZIP code. You can use a trailing \* wildcard, for example 787\* for Austin-area ZIPs.

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

Provider specialty or taxonomy description, for example Cardiovascular or Family Medicine. A trailing \* wildcard is added automatically if you do not include one (prefix match, e.g. Family Medicine\* or Cardiovascular\*).

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

Individuals (doctors, NPs, therapists) are NPI-1. Organizations (clinics, groups, hospitals) are NPI-2. Choose both to include everyone.

## `registeredAfter` (type: `string`):

Only include providers whose NPI enumeration date is on or after this day (YYYY-MM-DD). Useful for “new in the last 90 days” lead lists.

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

Stop after this many unique providers. Use a small number to estimate cost, then raise it for a full pull.

## `monitorMode` (type: `boolean`):

When enabled, only providers registered after the last successful run are returned. Schedule this actor daily or weekly in Apify Console to get a fresh-leads feed. The first monitor run returns the full matching set and then saves a cursor.

## Actor input object example

```json
{
  "state": "TX",
  "city": "Austin",
  "specialty": "Cardiovascular",
  "providerType": "both",
  "maxResults": 5,
  "monitorMode": false
}
```

# Actor output Schema

## `dataset` (type: `string`):

Dataset of healthcare provider records (NPI, specialty, location, phone).

# 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 = {
    "state": "TX",
    "city": "Austin",
    "specialty": "Cardiovascular",
    "maxResults": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("shrid5/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 = {
    "state": "TX",
    "city": "Austin",
    "specialty": "Cardiovascular",
    "maxResults": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("shrid5/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 '{
  "state": "TX",
  "city": "Austin",
  "specialty": "Cardiovascular",
  "maxResults": 5
}' |
apify call shrid5/npi-provider-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,shrid5/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/IUanXUMvYtPkvH2Fe/builds/Nbedb0nvghIZi4BSj/openapi.json