# New NPI Healthcare Providers - Doctor & Clinic Leads (`perskekits/npi-new-healthcare-providers`) Actor

Find newly registered healthcare providers from the official NPPES NPI Registry: name, credential, specialty, license, practice address and phone, authorized official. Filter by ZIP area, specialty and type. Leads for medical billing, credentialing and healthcare marketing.

- **URL**: https://apify.com/perskekits/npi-new-healthcare-providers.md
- **Developed by:** [PerskeKits](https://apify.com/perskekits) (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 $3.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

## New NPI Healthcare Providers - Doctor & Clinic Leads

Get healthcare providers that just received an NPI number - individuals and organizations - with specialty, practice address and phone from the official NPPES registry.

**Popular searches this Actor covers:** new NPI numbers, NPI registry scraper, new healthcare providers list, doctor leads, NPPES data export.

### What can you use it for?

- Medical billing, credentialing and EHR vendors
- Medical supply and pharma sales
- Healthcare staffing and malpractice insurance
- Market research on new practices by area

### Quick start (one click)

Press **Start** - the default input returns results in about a minute for a few cents. Example input:

```json
{
  "postalCodePrefixes": [
    "303"
  ],
  "daysBack": 30,
  "providerType": "all",
  "maxItems": 50
}
```

### Example output

| npi | providerType | primaryTaxonomy | enumerationDate | practiceCity | practiceState |
|---|---|---|---|---|---|
| 1982502746 | Individual | Behavior Technician | 2026-10-29 | ATLANTA | GA |
| 1932007937 | Individual | Nurse Practitioner, Gerontology | 2026-10-29 | ATLANTA | GA |
| 1912805912 | Individual | Surgery | 2026-10-29 | ATLANTA | GA |

Full records contain more fields (see the Output / Dataset tab). Download as **CSV, Excel, JSON** or use the Apify API, schedules and integrations (Zapier, Make, Google Sheets, webhooks).

### Pricing

Pay only for what you get (pay per event):

- **$0.003 per provider** returned
- **$0.005 per run start**

Examples: 100 providers = $0.305; 1,000 providers = $3.00. Apify free plan credits cover small runs.

### FAQ

**How do I target an area?**
Use postalCodePrefixes (3-digit ZIP prefixes, e.g. 303 = Atlanta).

**Can I filter specialty?**
Yes - use taxonomy, e.g. 'Dentist' or 'Nurse Practitioner'.

**Is this legal?**
It collects publicly available data only. You are responsible for using it in line with applicable laws (e.g. CAN-SPAM, GDPR, TCPA) and the source's terms.

**Can I schedule it?**
Yes - use Apify Schedules to run it daily and get new records automatically, then send them to Google Sheets, Slack or your CRM via integrations.

**Need a custom field, source or done-for-you list?**
Open an issue on the Issues tab - feature requests are welcome.

### Technical details

Find **newly registered healthcare providers** (new NPI numbers) in any area, straight from the official **CMS NPPES NPI Registry API**. Every doctor, nurse practitioner, dentist, therapist, pharmacy, clinic and home-health agency in the US needs an NPI to bill insurance, so a new NPI is one of the earliest public signals of a new practice or clinician.

**Who uses it:** medical billing and credentialing companies, healthcare staffing, EHR and practice-management software, medical supply reps, pharma marketing, malpractice insurance and healthcare real estate.

### How it works

The NPI Registry API can't filter by registration date and returns at most 1,200 records per query. The actor splits your ZIP prefixes into ever-smaller ZIP ranges until every query fits, reads the enumeration date of each provider, and keeps the ones registered in your date range. Only providers whose **practice location** is inside your ZIP prefixes are returned, newest first.

### Output

`npi`, `providerType` (Individual / Organization), `name`, `credential`, `enumerationDate`, `lastUpdated`, `status`, `soleProprietor`, `organizationSubpart`, `primaryTaxonomy`, `primaryTaxonomyCode`, `licenseNumber`, `licenseState`, `taxonomies`, `practiceStreet`, `practiceCity`, `practiceState`, `practiceZip`, `practicePhone`, `practiceFax`, `mailingAddress`, `authorizedOfficial` (organizations: name, title, phone), `otherNames`, `npiRegistryUrl`.

```json
{"npi": "1326963224", "providerType": "Individual", "name": "MATTIE FUERST", "credential": "FNP-C", "enumerationDate": "2026-08-11",
 "primaryTaxonomy": "Nurse Practitioner, Primary Care", "licenseNumber": "32414", "licenseState": "SC",
 "practiceStreet": "4300 HIGHWAY 90", "practiceCity": "CONWAY", "practiceState": "SC", "practiceZip": "29526-9630", "practicePhone": "(843) 399-3377"}
```

### Input

| Field | Default | Notes |
|---|---|---|
| `postalCodePrefixes` | `["303"]` | 2-5 digit ZIP prefixes of the practice location. A 3-digit prefix covers a metro area |
| `daysBack` | 30 | Enumerated in the last N days |
| `dateFrom` / `dateTo` | - | Exact enumeration-date range |
| `providerType` | all | `individual` (NPI-1) or `organization` (NPI-2) |
| `taxonomy` | - | NPPES specialty, e.g. `Dentist`, `Chiropractor`, `Nurse Practitioner*` (wildcard) |
| `maxItems` | 50 | Newest first |

**Speed:** a 3-digit metro prefix takes about 15-60 seconds. Adding a `taxonomy` or `providerType` filter makes runs much faster. Very large buildings (hospital campuses with more than 1,200 providers at one ZIP+4) can be partly missed; the run log warns when that happens.

### Pricing

Pay per result: one `result` event per provider.

# Actor input Schema

## `postalCodePrefixes` (type: `array`):

2-5 digit ZIP prefixes of the practice location, e.g. 303 (Atlanta), 100 (Manhattan), 33139. Shorter prefixes cover more area but take longer.

## `daysBack` (type: `integer`):

NPIs enumerated in the last N days (ignored if Date from is set).

## `dateFrom` (type: `string`):

Optional start of the enumeration-date range.

## `dateTo` (type: `string`):

Optional end of the enumeration-date range.

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

Individual clinicians, organizations, or both.

## `taxonomy` (type: `string`):

NPPES taxonomy description, e.g. Dentist, Nurse Practitioner, Physical Therapist, Chiropractor. Exact or with \* wildcard, e.g. Psych\*.

## `maxItems` (type: `integer`):

Newest NPIs first.

## Actor input object example

```json
{
  "postalCodePrefixes": [
    "303"
  ],
  "daysBack": 30,
  "providerType": "all",
  "maxItems": 50
}
```

# 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 = {
    "postalCodePrefixes": [
        "303"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("perskekits/npi-new-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 = { "postalCodePrefixes": ["303"] }

# Run the Actor and wait for it to finish
run = client.actor("perskekits/npi-new-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 '{
  "postalCodePrefixes": [
    "303"
  ]
}' |
apify call perskekits/npi-new-healthcare-providers --silent --output-dataset

```

## MCP server setup

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