# New Healthcare Provider Leads (NPPES New NPIs, No API Key) (`intenal_builds/nppes-new-provider-leads`) Actor

Doctors, NPs, therapists, dentists, clinics and agencies that just got a new NPI, from the official CMS NPPES weekly files. Specialty decoded, practice phone, address, license and authorized official. Filter by state, city, ZIP, specialty. Up to 12 weeks back.

- **URL**: https://apify.com/intenal_builds/nppes-new-provider-leads.md
- **Developed by:** [Jaydan Eaton](https://apify.com/intenal_builds) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.50 / 1,000 provider leads

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 Healthcare Provider Leads (NPPES New NPIs)

Every week CMS issues about **12,000 new NPIs**: newly licensed doctors, nurse practitioners, therapists, dentists, and brand-new practices, clinics, home health agencies and pharmacies. This actor reads the official **CMS NPPES weekly data dissemination files** and gives you just those new providers, cleaned and filterable. No API key, no login, no proxies.

### What you get per provider

- NPI, NPI issue date, individual or organization
- Name, credential (MD, NP, DDS, PT...), organization legal name and DBA
- **Specialty decoded** from the NUCC taxonomy (e.g. `363LF0000X` = Family Nurse Practitioner), all specialties, license number and state
- Practice address, **practice phone**, fax, mailing address
- For new organizations: **authorized official name, title and phone** (usually the owner)
- Link to the official NPI Registry record

### Who uses it

- Medical billing, credentialing and RCM companies (new practices need payer enrollment now)
- EHR / practice-management / telehealth software sales
- Malpractice and business insurance agents
- Medical supply, lab, pharmacy and staffing sales teams
- Healthcare market research (where new providers are opening)

### Filters

Weeks back (1 to 12), individuals vs organizations, states, cities, ZIP prefixes, specialty keywords (`dentist`, `home health`, `physical therapist`, `behavior analyst`...), exclude keywords, exact NUCC taxonomy codes, phone required, and optionally existing providers whose record was just updated.

### Example input

```json
{"weeksBack": 2, "entityType": "organization", "states": ["TX"], "specialtyKeywords": ["dentist", "home health"], "requirePhone": true, "maxResults": 500}
```

### Pricing

Pay per provider returned. Set **Max results** to cap spend.

### Data source and notes

Data comes from the public NPPES Downloadable File published by CMS at download.cms.gov/nppes (updated weekly, usually Monday). NPPES data is public under FOIA. Phone numbers are the business numbers providers filed with CMS. Use the data in line with applicable laws (TCPA, CAN-SPAM, state rules) and honor opt-outs. Not affiliated with CMS or NUCC.

# Actor input Schema

## `weeksBack` (type: `integer`):

How many of the latest CMS NPPES weekly files to read (each covers 7 days, about 12,000 new NPIs). 1 = newest week.

## `entityType` (type: `string`):

Individuals (doctors, NPs, therapists...) or organizations (new practices, clinics, agencies, pharmacies; include authorized official name, title, phone).

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

Practice-location state codes, e.g. TX, FL. Empty = all.

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

Practice-location cities (exact, case-insensitive). Empty = all.

## `zipPrefixes` (type: `array`):

Match practice ZIPs starting with these, e.g. 770 or 75201.

## `specialtyKeywords` (type: `array`):

Keep providers whose taxonomy/specialty or credential contains any keyword, e.g. dentist, chiropractor, nurse practitioner, physical therapist, home health, pharmacy, behavior analyst.

## `excludeKeywords` (type: `array`):

Drop providers whose specialties contain any of these, e.g. student, technician.

## `taxonomyCodes` (type: `array`):

Exact NUCC codes, e.g. 1223G0001X (general dentist), 363LF0000X (family NP).

## `requirePhone` (type: `boolean`):

Skip records without a practice-location phone.

## `includeUpdated` (type: `boolean`):

Off = only NPIs newly issued in the selected weeks. On = also existing providers whose record changed (new address, new specialty...). Check isNewProvider.

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

Stop after this many providers (you pay per provider).

## Actor input object example

```json
{
  "weeksBack": 1,
  "entityType": "all",
  "states": [
    "TX"
  ],
  "requirePhone": false,
  "includeUpdated": false,
  "maxResults": 100
}
```

# Actor output Schema

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

One item per newly issued NPI.

# 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 = {
    "weeksBack": 1,
    "states": [
        "TX"
    ],
    "maxResults": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("intenal_builds/nppes-new-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 = {
    "weeksBack": 1,
    "states": ["TX"],
    "maxResults": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("intenal_builds/nppes-new-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 '{
  "weeksBack": 1,
  "states": [
    "TX"
  ],
  "maxResults": 100
}' |
apify call intenal_builds/nppes-new-provider-leads --silent --output-dataset

```

## MCP server setup

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