# NPI Registry API & US Healthcare Provider Leads (`digital_influx/us-healthcare-providers`) Actor

Search the official NPI Registry of CMS by specialty, state, city or ZIP code: doctors, dentists, clinics and pharmacies with practice phone, fax, address, license and authorized official. Find new practices by NPI issue date.

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

## Pricing

from $3.00 / 1,000 provider saveds

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

## NPI Registry API & US Healthcare Provider Leads

**Search the official NPI Registry of the US government by specialty, state, city or ZIP code** and get every doctor, dentist, clinic, pharmacy, therapist and home health agency there, with:

- the practice phone, fax and address;
- the specialty (taxonomy) with its state license number;
- the authorized official of each organization, with title and phone;
- the date the NPI was issued, so you can find **new practices and newly licensed practitioners**.

No account, no API key, no proxies: the data comes from the NPPES NPI Registry API of the Centers for Medicare & Medicaid Services (CMS), which publishes it under the Freedom of Information Act and updates it daily.

### Who uses it

- **Healthcare suppliers and vendors** (dental and medical supplies, EHR and practice software, medical billing, credentialing, staffing, insurance): every practice of a specialty in a territory, with phone and the owner or administrator.
- **New-practice prospecting:** practices whose NPI was issued in the last weeks are opening now and buying equipment, software, insurance and marketing.
- **Recruiters and staffing agencies:** practitioners by specialty, credential and city.
- **Data teams:** verify and enrich lists of NPI numbers (name, specialty, license, address, status).

### What you get

One record per provider (NPI):

| Field | Example |
|---|---|
| `npi`, `providerType` | `1154494250`, `organization` (practices, clinics, groups) or `individual` (practitioners) |
| `name`, `organizationName`, `firstName`, `lastName`, `credential` | 360 DENTAL CARE P.A.; for people, KURT WILLIAM EDEKER, DC |
| `primarySpecialty`, `primaryTaxonomyCode` | Dentist, General Practice, 1223G0001X |
| `licenseNumber`, `licenseState` | 16292, TX |
| `specialties` | Every taxonomy of the provider, the primary one first |
| `phone`, `fax` | 512-327-3631, 512-327-2234 (of the primary practice location) |
| `address`, `address2`, `city`, `state`, `zip`, `zipPlus4` | 3660 STONERIDGE RD STE B101, AUSTIN, TX, 78746, 78746-7759 |
| `mailingAddress` | The mailing address on one line |
| `authorizedOfficialName`, `authorizedOfficialTitle`, `authorizedOfficialPhone`, `authorizedOfficialCredential` | MICHAEL B NUSSBAUM, President, 512-327-3631, D.D.S. (organizations) |
| `otherNames` | Doing-business-as and former names of organizations |
| `otherLocations` | Other practice locations with their phone |
| `endpoints` | Direct secure messaging addresses and other electronic endpoints the provider published |
| `soleProprietor` | For individuals: `true` when they practice as a sole proprietor |
| `enumerationDate`, `lastUpdated`, `status` | When the NPI was issued and last updated; `active` |
| `foundBy`, `registryUrl`, `retrievedAt` | The search that found it, the provider's page in the registry and when it was read |
| `change` | With *Only new*: `new` or `updated` |

Example record:

```json
{
  "npi": "1154494250",
  "providerType": "organization",
  "name": "360 DENTAL CARE P.A.",
  "primarySpecialty": "Dentist, General Practice",
  "licenseNumber": "16292",
  "licenseState": "TX",
  "phone": "512-327-3631",
  "fax": "512-327-2234",
  "address": "3660 STONERIDGE RD STE B101",
  "city": "AUSTIN",
  "state": "TX",
  "zip": "78746",
  "authorizedOfficialName": "MICHAEL B NUSSBAUM",
  "authorizedOfficialTitle": "President",
  "otherNames": [{ "type": "Doing Business As", "name": "MICHAEL B. NUSSBAUM D.D.S." }],
  "enumerationDate": "2006-11-16",
  "registryUrl": "https://npiregistry.cms.hhs.gov/provider-view/1154494250"
}
```

The **OUTPUT** record of each run has the totals per search, the count by specialty and by state, the inputs that were not valid and the attribution.

### Input

Dental practices around Austin (ZIP codes starting with 787) whose NPI was issued in the last year:

```json
{
  "taxonomies": ["Dentist"],
  "zipCodes": ["787"],
  "providerType": "organization",
  "enumeratedWithinDays": 365,
  "maxResults": 50
}
```

Chiropractors and physical therapists in two cities, only those with a practice phone:

```json
{
  "taxonomies": ["Chiropractor", "Physical Therapist"],
  "cities": ["Austin, TX", "Miami, FL"],
  "providerType": "individual",
  "onlyWithPhone": true,
  "maxResults": 500
}
```

Every new home health agency in Florida and Georgia this month:

```json
{
  "taxonomies": ["Home Health"],
  "states": ["FL", "GA"],
  "providerType": "organization",
  "enumeratedWithinDays": 30
}
```

Look up NPI numbers:

```json
{
  "npiNumbers": ["1154494250", "1003768524"]
}
```

| Field | What it does |
|---|---|
| `taxonomies` | Specialty descriptions as the registry writes them: Dentist, Chiropractor, Family Medicine, Nurse Practitioner, Pharmacy, Physical Therapist, Home Health... A trailing `*` after 2 letters is a wildcard. |
| `states`, `cities`, `zipCodes` | Places. Each one is a search of its own; a provider found twice is saved once. ZIP codes take 5 digits or the first 2 to 4. Places match the provider's primary practice location. |
| `providerType` | Organizations (NPI type 2), individuals (type 1) or both. |
| `enumeratedWithinDays` | Only providers whose NPI was issued in the last N days. |
| `primaryOnly` | The registry matches any of a provider's specialties; this keeps those whose primary specialty contains the words searched. |
| `onlyWithPhone` | Only providers with a practice phone. |
| `npiNumbers` | NPI numbers to look up, one request each. A number with a wrong check digit is reported and not asked. |
| `maxResults` | Providers saved in the run (1,000 by default), newest NPI first. |
| `onlyNew` + `memoryName` | For scheduled runs: only the providers that earlier runs of the same search did not save, or whose phone, address, primary specialty or status changed. |

### Only new or updated

With **Only new** and a weekly schedule, each run saves only the providers the earlier runs of the same search did not save, plus those whose practice phone, address, primary specialty or status changed. The memory lives in a key-value store named `us-healthcare-providers-state` in your account.

### How much it costs

Pay per event: **only for the providers saved**. Providers left out by the filters or already saved by an earlier run are free. Measured on 2026-10-02:

- Dental practices in ZIP codes 787\*: 502 read in 3 requests; 38 had an NPI issued in the last year.
- Dental practices in all of Texas with an NPI issued in the last 30 days: 10,222 read in 222 requests (about 5 minutes); 33 new.

### Use it from AI agents (MCP)

Claude, ChatGPT, Cursor and any other MCP client can run this Actor as a tool: add `https://mcp.apify.com?tools=digital_influx/us-healthcare-providers` as a remote MCP server and sign in with your Apify account. It is also one of the tools of US & UK Public Records MCP (`digital_influx/public-records-mcp`), by the same author, made for agents.

### Good to know

- **1,200 results a search.** The registry answers 200 results a request and lets a search go up to 1,200, in name order. When a search reaches that and the run needs more (a large state, or a date window that needs the whole search), the Actor narrows it by ZIP code (two digits, then one more) and reads the parts, so no provider is left out. A single 5-digit ZIP code with more than 1,200 providers of one search keeps the first 1,200 by name, and the OUTPUT says so.
- **The registry has no date filter.** With *NPI issued within*, the whole search is read and filtered here: a state takes a few minutes, a city or ZIP code seconds.
- **Specialties** are matched by the registry against any of a provider's taxonomies. "Dentist" finds every dental specialization; use *Only when it is the primary specialty* for a narrower list.
- **The data is what providers report to NPPES.** Phones and addresses are the ones on their NPI record, and some are out of date. Credentials are written as each provider typed them (DC, D.C., D. C).
- **Requests:** at most 2 a second, with a budget of 2,000 a run.

### Source and attribution

Centers for Medicare & Medicaid Services (CMS), National Plan and Provider Enumeration System (NPPES), NPI Registry API version 2.1 (https://npiregistry.cms.hhs.gov). The registry shows the data disclosable under the Freedom of Information Act and updates it daily. CMS does not endorse this Actor or the uses of its results.

# Actor input Schema

## `taxonomies` (type: `array`):

Provider taxonomy descriptions, e.g. Dentist, Chiropractor, Physical Therapist, Nurse Practitioner, Family Medicine, Pharmacy, Home Health. A trailing \* after 2 letters works as a wildcard (Ortho\*). Each specialty is searched in each place.

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

2-letter codes, e.g. TX, CA, FL. Each state is a search of its own.

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

City and state, e.g. Austin, TX. Without the state, the city is searched in every state.

## `zipCodes` (type: `array`):

5-digit ZIP codes, or their first 2 to 4 digits for a wider area (e.g. 787 for Austin).

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

Organizations are practices, clinics, groups and pharmacies (NPI type 2); individuals are practitioners (NPI type 1).

## `enumeratedWithinDays` (type: `integer`):

Keep only providers whose NPI was issued in the last N days: new practices and newly licensed practitioners. The registry has no date filter, so the whole search is read; a state takes a few minutes.

## `primaryOnly` (type: `boolean`):

The registry matches any of a provider's specialties. This keeps those whose primary specialty contains the words searched.

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

Save only providers that list a practice location phone.

## `npiNumbers` (type: `array`):

10-digit NPI numbers to verify or enrich, one request each. Numbers with a wrong check digit are reported as invalid.

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

Providers saved in this run, newest NPI first. You also never pay more than the spending limit you set for the run.

## `onlyNew` (type: `boolean`):

Save only providers that earlier runs of this same search did not save, or whose practice phone, address, primary specialty or status changed since (each row says which). Schedule it weekly. The memory lives in a key-value store named "us-healthcare-providers-state" in your account.

## `memoryName` (type: `string`):

By default each search has its own memory. Give a name to share one memory between tasks, or a new name to start over.

## Actor input object example

```json
{
  "taxonomies": [
    "Dentist"
  ],
  "zipCodes": [
    "787"
  ],
  "providerType": "organization",
  "enumeratedWithinDays": 365,
  "primaryOnly": false,
  "onlyWithPhone": false,
  "maxResults": 50,
  "onlyNew": false
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (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 = {
    "taxonomies": [
        "Dentist"
    ],
    "zipCodes": [
        "787"
    ],
    "providerType": "organization",
    "enumeratedWithinDays": 365,
    "maxResults": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("digital_influx/us-healthcare-providers").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 = {
    "taxonomies": ["Dentist"],
    "zipCodes": ["787"],
    "providerType": "organization",
    "enumeratedWithinDays": 365,
    "maxResults": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("digital_influx/us-healthcare-providers").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 '{
  "taxonomies": [
    "Dentist"
  ],
  "zipCodes": [
    "787"
  ],
  "providerType": "organization",
  "enumeratedWithinDays": 365,
  "maxResults": 50
}' |
apify call digital_influx/us-healthcare-providers --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,digital_influx/us-healthcare-providers"
        }
    }
}
```

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/Kjq7zrYSvdUF31bIZ/builds/Um32SzlLPArcLU112/openapi.json