# NPI Registry Lookup API: NPPES Provider Search & Verify (`clearpathdata/npi-registry-lookup`) Actor

Verify NPI numbers or search US doctors, nurses, pharmacies and organizations by name, specialty, city, state or ZIP with CMS's official NPPES API. Phone, address, taxonomy. $2 per 1,000.

- **URL**: https://apify.com/clearpathdata/npi-registry-lookup.md
- **Developed by:** [Six Figure Salute](https://apify.com/clearpathdata) (community)
- **Categories:** Business, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 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.

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 Lookup API: NPPES Provider Search & Verify

Verify NPI numbers or search US doctors, nurses, pharmacies and organizations by name, specialty, city, state or ZIP with CMS's official NPPES API. Phone, address, taxonomy. $2 per 1,000.

### What does it do?

**NPI Registry Lookup** verifies National Provider Identifier (NPI) numbers and searches the CMS **NPPES NPI Registry** for US healthcare providers and organizations by name, specialty (taxonomy), city, state or ZIP. You get name, credential, status, primary taxonomy, license, practice address and phone.

- ✅ Official public data source: no login, no cookies, no proxies
- ✅ Fast: plain API calls, typical runs finish in seconds
- ✅ Clean, flat JSON / CSV / Excel output, ready for Sheets, BI tools or AI agents
- ✅ Pay only for results: no monthly rental

### Use cases

- **Healthcare sales & marketing:** build provider lead lists by specialty and area.
- **Credentialing & payers:** bulk-verify NPIs.
- **Healthtech:** enrich provider records.

### How to use it

1. Click **Try for free**. The input is prefilled with a working example.
2. Edit the input (see examples below) and click **Start**.
3. Download results as JSON, CSV, Excel or HTML, or pull them via API.

### Input examples

**Verify an NPI**

```json
{
  "npiNumbers": [
    "1003000126"
  ]
}
```

**Pharmacies in Colorado**

```json
{
  "taxonomy_description": "Pharmacy",
  "state": "CO",
  "maxResults": 20
}
```

### Output

Sample rows:

| npi | name | credential | primaryTaxonomy | city | state | phone |
|---|---|---|---|---|---|---|
| 1003000126 | ARDALAN ENKESHAFI | M.D. | Hospitalist | BETHESDA | MD | 443-602-6207 |
| 1336910033 | 1918 WINTER STREET OPERATING CO LLC |  | Pharmacy, Community/Retail Pharmacy | AURORA | CO | 303-400-4880 |

Sample JSON record (long fields shortened):

```json
{
  "query": "1003000126",
  "found": true,
  "npi": "1003000126",
  "entityType": "Individual",
  "name": "ARDALAN ENKESHAFI",
  "credential": "M.D.",
  "status": "A",
  "enumerationDate": "2007-08-31",
  "lastUpdated": "2025-05-28",
  "primaryTaxonomyCode": "208M00000X",
  "primaryTaxonomy": "Hospitalist",
  "licenseState": "DC",
  "licenseNumber": "MD600003480",
  "practiceAddress": "6410 ROCKLEDGE DR STE 304",
  "city": "BETHESDA",
  "state": "MD",
  "postalCode": "20817",
  "phone": "443-602-6207",
  "allTaxonomies": [
    "207R00000X Internal Medicine",
    "207R00000X Internal Medicine",
    "207R00000X Internal Medicine",
    "..."
  ],
  "otherIdentifiers": [],
  "registryUrl": "https://npiregistry.cms.hhs.gov/provider-view/1003000126",
  "source": "CMS NPPES NPI Registry API v2.1"
}
```

### Pricing

Pay per event: **$0.002 per provider record** ($2.00 per 1,000). No start fee, no monthly rental. Rows for not-found inputs and errors are free.

| Results | Cost |
|---|---|
| 100 provider records | $0.20 |
| 1,000 provider records | $2.00 |
| 10,000 provider records | $20.00 |

Apify's free plan includes monthly platform credit, so you can try it at no cost.

### Integrations

- **Google Sheets:** use Apify's Google Sheets integration, or import the dataset CSV link with `=IMPORTDATA()`.
- **Zapier & Make:** trigger runs and receive the dataset via the official Apify apps.
- **Webhooks & schedules:** run daily or hourly and post results anywhere.
- **AI agents (MCP):** available to Claude, ChatGPT and other agents through the Apify MCP server.
- **API & SDKs:** call from Python, JavaScript or any HTTP client:

```bash
curl -X POST 'https://api.apify.com/v2/acts/clearpathdata~npi-registry-lookup/run-sync-get-dataset-items?token=<YOUR_API_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{"npiNumbers": ["1003000126"]}'
```

### FAQ

**Is it the official registry?**

Yes, CMS's public NPPES API.

**Max results?**

NPPES caps results per query; narrow by city or ZIP for large areas.

**Something not working?**

Open an issue on the Actor's Issues tab, and it will be fixed quickly.

### More details

Verify NPI numbers or search US healthcare providers and organizations by name, specialty, city, state or ZIP using CMS's official NPPES API.

Look up and verify **National Provider Identifier (NPI)** numbers, or search the **NPPES NPI Registry** by name, specialty (taxonomy), city, state, ZIP and entity type. Returns clean, flat records.

**Uses:** claims and credentialing checks, provider data cleanup, payer/pharmacy ops, building directories of healthcare organizations, health-tech prototypes.

##### Output fields

NPI, individual/organization, name, credential, status, enumeration/last-updated dates, primary taxonomy code and description, license state/number, practice address, phone, all taxonomies, other identifiers, registry link.

##### Source and terms

Live from CMS's public NPPES NPI Registry API v2.1 (`npiregistry.cms.hhs.gov/api`). This is public data that CMS publishes for provider identification. Use it to verify and identify providers, not for unsolicited marketing. Not affiliated with CMS/HHS.

##### Pricing

Pay per event: **provider**. Charged per NPI provider record returned. You pay only for results. Not-found/error rows are free. Apify platform usage is included.

##### Example input

```json
{
  "npiNumbers": [
    "1003000126",
    "0000000000"
  ],
  "taxonomy_description": "Pharmacy",
  "city": "Aurora",
  "state": "CO",
  "maxResults": 5
}
```

Built by clearpathdata, a maker of official-government-data Actors. Questions and feature requests are welcome in the Issues tab.

# Actor input Schema

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

10-digit NPIs to verify/enrich.

## `organization_name` (type: `string`):

Search organizations (wildcard \* after 2 chars).

## `first_name` (type: `string`):

Individual first name.

## `last_name` (type: `string`):

Individual last name.

## `taxonomy_description` (type: `string`):

e.g. Cardiology, Pharmacy, Physical Therapist.

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

City.

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

2-letter state code (needs at least one other criterion).

## `postal_code` (type: `string`):

5 or 9 digit ZIP (wildcard allowed).

## `enumeration_type` (type: `string`):

NPI-1 individuals, NPI-2 organizations.

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

NPPES API caps searches at 1,200 results.

## Actor input object example

```json
{
  "npiNumbers": [
    "1003000126"
  ],
  "taxonomy_description": "Pharmacy",
  "state": "CO",
  "maxResults": 20
}
```

# 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 = {
    "npiNumbers": [
        "1003000126"
    ],
    "taxonomy_description": "Pharmacy",
    "state": "CO",
    "maxResults": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("clearpathdata/npi-registry-lookup").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 = {
    "npiNumbers": ["1003000126"],
    "taxonomy_description": "Pharmacy",
    "state": "CO",
    "maxResults": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("clearpathdata/npi-registry-lookup").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 '{
  "npiNumbers": [
    "1003000126"
  ],
  "taxonomy_description": "Pharmacy",
  "state": "CO",
  "maxResults": 20
}' |
apify call clearpathdata/npi-registry-lookup --silent --output-dataset

```

## MCP server setup

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

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/7kghPLh4RrG25ICYF/builds/dMJzpINm7s6WPcJZE/openapi.json
