# New NPI Numbers: Newly Registered Medical Practices & Doctors (`quarrylane-data/nppes-npi-new-provider-leads`) Actor

New NPI numbers from the official CMS NPPES weekly file: newly registered medical practices (NPI-2) and optionally new doctors and providers (NPI-1). Filter by date, specialty taxonomy, state, city. For healthcare sales leads. No API key.

- **URL**: https://apify.com/quarrylane-data/nppes-npi-new-provider-leads.md
- **Developed by:** [Quarrylane Data](https://apify.com/quarrylane-data) (community)
- **Categories:** Lead generation, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.50 / 1,000 provider records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## NPPES NPI Newly Enumerated Practices & Providers

A **new-enumeration feed** of US medical practices and (optionally) individual providers from the official CMS [NPPES weekly incremental file](https://download.cms.gov/nppes/NPI_Files.html). Each run returns NPIs whose **enumeration date** falls in your window — not an 8-million-row dump of the entire registry.

By default you get **organizations only (NPI-2)**: legal business name, authorized official, practice and mailing address, phone, taxonomies and the official NPI Registry URL. Individual (NPI-1) records are public federal data but are consumer-adjacent, so they are **opt-in** and limited to professional fields (name, credential, taxonomy, license, practice location and practice phone — no sex and no mailing address).

No CMS login and no API key. This Actor never downloads the 1 GB monthly full file.

### What does this Actor do?

Healthcare sales, credentialing and staffing teams buy a list of **practices that just appeared in NPPES**. The official NPI Registry API cannot search by enumeration date and caps each query at 1,200 rows. CMS already publishes those new and updated NPIs as a small weekly zip (~6–15 MB). This Actor reads the official index, downloads the current weekly incremental V.2 file, keeps rows whose enumeration date is in your window, and returns **one normalized row per NPI**.

Typical weeks contain a few thousand new organizations. Updates to older NPIs in the same weekly file are ignored unless their enumeration date is also in the window.

### Who uses it?

- **Medical sales and lab/imaging reps** who want new clinics in a state or specialty
- **Credentialing and payer network teams** watching a taxonomy or territory
- **Clay, n8n and Make** workflows that drop new practices into a CRM every week

### Input

| Field | What it does |
|---|---|
| `daysBack` / `startDate` / `endDate` | Enumeration-date window. Default: last **21 days**, so a daily auto-test still overlaps the latest weekly file. |
| `entityType` | Default **`organizations`** (NPI-2). Set `individuals` or `both` to opt in to NPI-1 professional records. |
| `taxonomies` | NUCC codes (e.g. `261QU0200X`) or text such as `Family Medicine`. |
| `states`, `cities` | Primary practice location. |
| `activeOnly` | Default true; skips deactivated NPIs. |
| `onlyNew` + `monitorName` | Monitor mode: later runs return (and charge for) only NPIs not seen before. The first run bills up to `maxItems` as standard records and seeds the rest of the current window without charging. |
| `maxItems` | Default **25** (auto-test safe). Free plans are capped at 15. Paid plans can go up to 20,000. |

#### Example input

```json
{
  "daysBack": 21,
  "entityType": "organizations",
  "states": ["TX"],
  "taxonomies": ["Family Medicine"],
  "maxItems": 25
}
```

### Output

Each record includes `npi`, `entityType` (`NPI-2` or `NPI-1`), `organizationName` or professional `providerName`, `enumerationDate`, `primaryTaxonomy` / `taxonomies` (with license and state when present), practice address, city, state, ZIP and phone, authorized official (organizations), and `npiRegistryUrl` (for example `https://npiregistry.cms.hhs.gov/provider-view/1972402626`). EIN and tax IDs are never included.

Sample from a real run of this Actor (person-name and personal contact fields masked in this README only; long text and lists shortened):

```json
{
  "recordId": "1528968161",
  "npi": "1528968161",
  "entityType": "NPI-2",
  "entityTypeLabel": "Organization",
  "status": "Active",
  "enumerationDate": "2026-11-07",
  "lastUpdateDate": "2026-11-07",
  "certificationDate": "2026-11-07",
  "organizationName": "NEW LEVEL MUSIC ACADEMY",
  "otherNames": [],
  "isOrganizationSubpart": false,
  "parentOrganizationName": null,
  "providerName": null,
  "providerFirstName": null,
  "providerLastName": null,
  "providerCredential": null,
  "authorizedOfficial": "(masked in this README sample)",
  "practiceAddress": "2127 W MADISON ST APT 401",
  "practiceCity": "CHICAGO",
  "practiceState": "IL",
  "practiceZip": "60612",
  "practicePostalCode": "606125626",
  "practiceCountry": "US",
  "practicePhone": "7733860063",
  "practiceFax": null,
  "primaryTaxonomyCode": "332B00000X",
  "primaryTaxonomy": "Durable Medical Equipment & Medical Supplies",
  "taxonomies": [
    {
      "code": "332B00000X",
      "description": "Durable Medical Equipment & Medical Supplies",
      "licenseNumber": null,
      "licenseState": null,
      "primary": true
    }
  ],
  "npiRegistryUrl": "https://npiregistry.cms.hhs.gov/provider-view/1528968161",
  "source": "NPPES",
  "sourceFile": "weekly-incremental",
  "mailingAddress": "2127 W MADISON ST APT 401",
  "mailingCity": "CHICAGO",
  "mailingState": "IL",
  "mailingZip": "60612",
  "mailingPhone": "7733860063",
  "scrapedAt": "2026-11-13T04:39:43.852Z",
  "sourceWeekStart": "2026-11-02",
  "sourceWeekEnd": "2026-11-08",
  "sourceFileName": "NPPES_Data_Dissemination_110226_110826_Weekly_V2.zip"
}
```

### Pricing

Pay per result, with no monthly rental:

| Event | Price |
|---|---|
| Provider record (`provider-record`) | **$5.00 per 1,000 records** |
| New-provider lead (`new-provider`, later monitor-mode runs) | **$25.00 per 1,000 records** |

The first monitor run is billed as standard provider records (up to `maxItems`). Remaining current matches in the window are remembered but not charged, so later scheduled runs only return new NPIs. Set **Max cost per run** for a hard budget. Free Apify plans are capped at 15 results per run.

#### Price per event and Store discounts

| Event | Charged for | Free plan | Bronze | Silver | Gold | Per 1,000 (Free plan) |
|---|---|---|---|---|---|---|
| Provider record (`provider-record`) | Charged for each newly enumerated NPI saved to your dataset in a standard run, including the first run of a new-provider monitor. | $0.005 | $0.0045 | $0.004 | $0.0035 | $5.00 |
| New-provider lead (monitor) (`new-provider`) | Charged instead of the standard record for each NPI delivered on a later run when monitor mode (onlyNew) is on and this monitor name has already been used. | $0.025 | $0.0225 | $0.02 | $0.0175 | $25.00 |

Prices are in USD per event. This Actor is pay-per-event only: there is no monthly rental and no separate platform usage charge on top, because compute is included in the event price. Apify Bronze, Silver and Gold subscribers get the discounted prices automatically. Set **Max cost per run** in the run options to cap spend, and the Actor stops before it goes over.

### Source and lag

CMS currently publishes **only the latest weekly incremental zip** on the [NPI Files](https://download.cms.gov/nppes/NPI_Files.html) page (Version 2). Older weekly URLs return 404, and this Actor does not download the monthly full replacement (~1 GB compressed). That means the feed lags the live registry by up to about a week, and a custom date window that does not overlap the published week returns no rows. If you leave the dates at their defaults and the 21-day window ever misses the listed file, the Actor falls back to that file's own week so a default run still returns data.

The NPI Registry API is refreshed daily but **cannot filter by enumeration date**, so it is not used here.

Issuance of an NPI does not mean the provider is licensed or credentialed.

### How to automate with Clay.com, n8n, Make, and Claude MCP

All examples use this Actor's Store ID `quarrylane-data/nppes-npi-new-provider-leads`. Replace `YOUR_APIFY_TOKEN` with your Apify API token (Console → Settings → API & Integrations). Never paste a token into a public workflow.

#### Official Apify API (run-sync-get-dataset-items)

```bash
curl -sS -X POST \
  "https://api.apify.com/v2/acts/quarrylane-data~nppes-npi-new-provider-leads/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"daysBack":21,"entityType":"organizations","states":["TX"],"maxItems":15}'
```

The same URL works from any HTTP client. Use `~` between the username and Actor name. For a weekly monitor, pass `"onlyNew": true` and a stable `"monitorName"`.

#### n8n

- **Apify node** (community, `n8n-nodes-apify`): add the Apify credentials, choose **Run Actor**, set the Actor to `quarrylane-data/nppes-npi-new-provider-leads`, and paste the JSON input above into the Actor input field. Use the node's "wait for finish" option, then read the default dataset.
- **HTTP Request node**: Method `POST`, URL `https://api.apify.com/v2/acts/quarrylane-data~nppes-npi-new-provider-leads/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN`, header `Content-Type: application/json`, body as JSON.

#### Make (Integromat)

Use the **Apify** module's **Run an Actor** action (or an HTTP module with the endpoint above). After the run finishes, use **Get Dataset Items** on the default dataset, or call `run-sync-get-dataset-items` in a single HTTP module.

#### Clay.com

Add an **HTTP API** enrichment column:

- Method: `POST`
- URL: `https://api.apify.com/v2/acts/quarrylane-data~nppes-npi-new-provider-leads/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN`
- Headers: `Content-Type: application/json`
- Body: `{"daysBack":21,"entityType":"organizations","states":["TX"],"taxonomies":["Family Medicine"],"maxItems":15}`

Map `organizationName`, `practiceCity`, `practicePhone`, `primaryTaxonomy`, `enumerationDate` and `npiRegistryUrl` into Clay columns. Keep `maxItems` small in table-wide enrichments.

#### Claude and the Apify MCP server

This Actor is MCP-compatible (limited permissions). Point Claude, Cursor, or any MCP client at Apify's hosted server and include this Actor in the `tools` query parameter:

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=quarrylane-data/nppes-npi-new-provider-leads"
    }
  }
}
```

On first connect, sign in to Apify (OAuth) or send an `Authorization: Bearer YOUR_APIFY_TOKEN` header. In Claude, you can also add `https://mcp.apify.com?tools=quarrylane-data/nppes-npi-new-provider-leads` as a custom connector under Settings → Connectors. Then ask Claude to "list newly enumerated medical practices in Texas from the official NPI weekly file."

### Is it legal to use this data?

Yes. NPPES is the official public FOIA dissemination of the National Provider Identifier registry, operated by CMS. The Actor uses the documented weekly incremental file, identifies itself, and never logs in. Default output is **business / practice records**. Individual NPI-1 rows, when you opt in, are limited to professional registry fields.

Built by **Quarrylane Data**. Not affiliated with CMS or NPPES. Data comes from the public weekly files at download.cms.gov/nppes.

### More US public-record lead data by Quarrylane Data

| Actor | What you get |
|---|---|
| [NYS Contract Reporter Bids & RFPs](https://apify.com/quarrylane-data/nys-contract-reporter-bids-scraper) | New York State government bids, RFPs, RFQs and grants with due dates and links |
| [US Contractor License Leads (9 states)](https://apify.com/quarrylane-data/us-contractor-license-leads) | Official contractor licences from 9 state registries with phone, address and status |
| [MWBE, DBE & Diversity-Certified Business Leads](https://apify.com/quarrylane-data/us-diversity-certified-business-leads) | Officially certified minority, women-owned and disadvantaged businesses |
| [Texas TDLR Contractor License Leads](https://apify.com/quarrylane-data/texas-tdlr-contractor-license-leads) | Texas TDLR licence holders (HVAC, electricians and more) with phone and address |
| [US Federal Contract Awards (USAspending)](https://apify.com/quarrylane-data/usaspending-federal-contract-awards) | Recent federal prime contract awards and the companies that won them |
| [FMCSA New Authority Leads](https://apify.com/quarrylane-data/fmcsa-new-authority-leads) | Newly granted USDOT / MC trucking authorities with carrier census details |
| [EPA Enforcement Case Leads](https://apify.com/quarrylane-data/epa-enforcement-case-leads) | EPA and state environmental enforcement cases with penalties and facilities |
| [OCC Bank Applications Monitor](https://apify.com/quarrylane-data/occ-bank-applications-monitor) | OCC bank charter, branch, merger and control applications |
| [Federal Reserve Bank M\&A Applications](https://apify.com/quarrylane-data/fed-bank-holding-company-applications) | Federal Reserve bank holding company formation, acquisition and merger filings |

# Actor input Schema

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

Used when startDate is empty. Default 21 days so the run overlaps the latest CMS weekly incremental file. CMS currently hosts only the latest weekly zip (not the 1 GB monthly file).

## `startDate` (type: `string`):

YYYY-MM-DD. Inclusive. If both dates are omitted, daysBack is used. If your window does not overlap the published weekly file, the run returns no rows (unless you left the dates at their defaults, in which case the latest week is used).

## `endDate` (type: `string`):

Last enumeration date to include, as YYYY-MM-DD (inclusive). Defaults to today.

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

Default organizations (NPI-2). Individual NPI-1 records are public federal registry data but are consumer-adjacent; they are opt-in and the Actor emits professional fields only (no sex or mailing address).

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

NUCC taxonomy codes (e.g. 261QU0200X) or text such as 'Family Medicine' or 'Clinic'. Matched against the official taxonomy code, display name, classification and specialization.

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

Two-letter US states of the primary practice location (e.g. TX, CA).

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

Only return providers whose practice location is in these cities (case-insensitive). Leave empty for all.

## `activeOnly` (type: `boolean`):

Skip deactivated NPIs (those with a deactivation date and no later reactivation).

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

Later runs return only NPIs not seen before under this monitor key. The first run bills up to maxItems as standard records and seeds the rest of the current window without charging.

## `monitorName` (type: `string`):

Label for this saved monitor (plain text, not a password or API key). When "Only new" monitor mode is on, the Actor remembers which records it has already delivered under this name and returns only new ones next time. Use a different name per filter set or client, for example "client-a-weekly". Older inputs that use monitorKey still work.

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

Default 25 (auto-test safe). Free Apify plans are capped at 15. Paid plans can go up to 20,000. A typical weekly file contains a few thousand new organizations.

## Actor input object example

```json
{
  "daysBack": 21,
  "entityType": "organizations",
  "activeOnly": true,
  "onlyNew": false,
  "monitorName": "default",
  "maxItems": 25
}
```

# Actor output Schema

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

Newly enumerated NPI records (organization or professional individual fields, taxonomy, practice location, dates and NPI Registry URL).

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("quarrylane-data/nppes-npi-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("quarrylane-data/nppes-npi-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 '{}' |
apify call quarrylane-data/nppes-npi-new-provider-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,quarrylane-data/nppes-npi-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/p977ZrDZBNJe9hTqd/builds/PWsJa1LXdAAeoRdQu/openapi.json
