# NPI / NPPES Healthcare Provider Registry Lookup (`bovi/npi-nppes-registry`) Actor

Look up US healthcare providers and organizations in the official CMS NPI Registry (NPPES). Search by NPI number, name, organization, specialty/taxonomy, or location. Returns NPI number, status, name, specialty, and practice address.

- **URL**: https://apify.com/bovi/npi-nppes-registry.md
- **Developed by:** [Vitalii Bondarev](https://apify.com/bovi) (community)
- **Categories:** Lead generation, Business
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.60 / 1,000 npi / nppes healthcare provider registry lookups

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

## NPI / NPPES Healthcare Provider Registry Lookup

Search the official US **NPI Registry** ([npiregistry.cms.hhs.gov](https://npiregistry.cms.hhs.gov/api-page)) —
the National Provider Identifier database run by **CMS** (Centers for
Medicare & Medicaid Services, **NPPES** = National Plan and Provider
Enumeration System). Look up a healthcare **provider** (an individual
clinician) or **organization** (a hospital, clinic, or group practice) by
exact NPI number, name, organization name, specialty/taxonomy, or practice
location. Returns the NPI number, status, name, specialty, and practice
address.

Typical use: verify a provider's or organization's NPI, specialty and
practice address for credentialing, referral routing, insurance-network
directory building, or healthcare lead generation.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `npiNumber` | string | — | Exact 10-digit NPI. Overrides all other search fields when set. |
| `firstName` | string | — | Individual provider's first name (trailing wildcard supported, e.g. `"John*"`). NPI-1 only. |
| `lastName` | string | — | Individual provider's last name (trailing wildcard supported). NPI-1 only. |
| `organizationName` | string | `"Hospital"` | Organization name (trailing wildcard supported). NPI-2 only. |
| `taxonomyDescription` | string | — | Specialty/taxonomy description (e.g. `"Cardiology"`, `"Nurse Practitioner"`, `"Pediatrics"`). |
| `city` | string | — | Practice-address city. |
| `state` | string | `"CA"` | Practice-address state, 2-letter code. |
| `postalCode` | string | — | Practice-address ZIP code. |
| `enumerationType` | string | `""` (both) | `"NPI-1"` = individuals only, `"NPI-2"` = organizations only, blank = both. |
| `maxItems` | integer | `50` | Cap on records returned. The NPPES API caps any single query at ~1,200 reachable rows (200/page × up to 6 pages) — narrow the search (add a state or taxonomy filter) to reach deeper into a large result set. |
| `proxyConfiguration` | object | Apify Proxy, RESIDENTIAL | Standard Apify Proxy input. The actor works out of the box — no proxy key or credentials of your own are required. |

At least one search field (besides `maxItems`/`enumerationType`/
`proxyConfiguration`) must be non-empty — NPPES rejects an all-blank query.

### Output fields

One record per matched provider or organization.

| Field | Description |
|---|---|
| `npi_number` | 10-digit National Provider Identifier |
| `enumeration_type` | `NPI-1` (individual) or `NPI-2` (organization) |
| `is_organization` | `true` for NPI-2, `false` for NPI-1 |
| `provider_name` | Individual full name (NPI-1) or organization name (NPI-2) |
| `first_name` / `last_name` | Individual name parts — empty for organization records |
| `credential` | Professional credential (MD, NP, DO, RN, ...) — individual records only |
| `status` | `Active` or `Inactive` |
| `practice_address_1` / `practice_city` / `practice_state` / `practice_postal_code` / `practice_phone` | Primary practice-location address |
| `mailing_city` / `mailing_state` | Mailing address, when distinct from practice location |
| `primary_taxonomy_code` / `primary_taxonomy_desc` / `primary_taxonomy_license` / `primary_taxonomy_state` | Primary specialty (NUCC taxonomy code, description, state license number, licensing state) |
| `all_taxonomies` | All specialty/taxonomy descriptions on file, semicolon-separated |
| `enumeration_date` | Date the NPI was first assigned |
| `last_updated` | Date the NPPES record was last updated |
| `npi_profile_url` | Direct link to the provider/organization's public NPI Registry page |

### PII disclosure

**Individual (NPI-1) records** carry the healthcare provider's own first
and last name, as a licensed professional, in a **federally mandated
public directory**. This is the same legal class of disclosure as this
fleet's `cslb-contractor-licenses` actor (US state contractor-license
registry) and `wyoming-sos-registry` actor (Secretary-of-State filings) —
a professional's identity published by design so patients, insurers, and
clearinghouses can verify who is treating them and where. The NPI Registry
public lookup exists **specifically** for this purpose
([npiregistry.cms.hhs.gov](https://npiregistry.cms.hhs.gov)) — it is not
personal data collected from a private source, and this actor surfaces
nothing beyond what CMS already publishes at that public URL for every
query.

**Organization (NPI-2) records carry no individual PII at all** — only the
organization's name, status, taxonomy, and practice address (the
`authorized_official_*` fields NPPES also returns for NPI-2 records are
deliberately **not** exposed by this actor's output, since that named
individual is a business contact rather than the subject of the lookup).

### Charge event

This actor bills per matched provider/organization record delivered:

- **`provider-record`** — charged once per record pushed to the dataset
  (individual or organization, whichever `enumerationType` matched).

### Notes

- `taxonomyDescription`, `firstName`, `lastName`, and `organizationName`
  support a trailing wildcard (`*`) per the NPPES API's own search syntax
  (e.g. `organizationName: "St Mary*"`).
- Pagination follows NPPES's own `skip`/`limit` mechanics up to its hard
  ceiling (`limit` max 200/request, `skip` max 1000) — at most ~1,200 rows
  are reachable per query regardless of `maxItems`. Add a `state`, `city`,
  or `taxonomyDescription` filter to search a narrower, fully-reachable
  slice of a large result set (e.g. a common surname nationwide).
- `npiNumber` is an exact match and the fastest, most unambiguous lookup —
  prefer it whenever the NPI is already known.

# Actor input Schema

## `npiNumber` (type: `string`):

Look up a single exact 10-digit National Provider Identifier. Overrides all other search fields when set.

## `firstName` (type: `string`):

Individual provider's first name. Supports a trailing wildcard (e.g. "John\*"). Only matches NPI-1 (individual) records.

## `lastName` (type: `string`):

Individual provider's last name. Supports a trailing wildcard (e.g. "Smi\*"). Only matches NPI-1 (individual) records.

## `organizationName` (type: `string`):

Healthcare organization name (hospital, clinic, group practice). Supports a trailing wildcard (e.g. "St Mary\*"). Only matches NPI-2 (organization) records.

## `taxonomyDescription` (type: `string`):

Provider specialty or taxonomy description (e.g. "Cardiology", "Nurse Practitioner", "Pediatrics"). Matches the NUCC taxonomy description text.

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

Filter by practice-address city.

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

Filter by practice-address state (e.g. TX, CA, NY).

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

Filter by practice-address ZIP code (5-digit or 5+4).

## `enumerationType` (type: `string`):

NPI-1 = individual provider only. NPI-2 = organization only. Leave blank to search both.

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

Maximum number of provider/organization records to return. The NPPES API caps any single query at ~1,200 reachable rows (200 per page × 6 pages) — narrow the search (add a state or taxonomy filter) to go deeper.

## `proxyConfiguration` (type: `object`):

Apify proxy used to reach the API. The actor works out of the box — no proxy key or credentials of your own are required; this is just Apify's standard rotating exit.

## Actor input object example

```json
{
  "organizationName": "Hospital",
  "state": "CA",
  "enumerationType": "",
  "maxItems": 50,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

Dataset of NPI/NPPES records (npi\_number, enumeration\_type, provider\_name, status, primary\_taxonomy\_desc, practice\_city, practice\_state, npi\_profile\_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 = {
    "organizationName": "Hospital",
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("bovi/npi-nppes-registry").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 = {
    "organizationName": "Hospital",
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("bovi/npi-nppes-registry").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 '{
  "organizationName": "Hospital",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call bovi/npi-nppes-registry --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bovi/npi-nppes-registry"
        }
    }
}

```

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/F3DpXrbeJuV1pkcOH/builds/GvYc7RiQoBiYvxZe9/openapi.json