# NPI Registry API - Healthcare Provider Lookup & Enrichment (`makework36/npi-registry-api`) Actor

Search 6M+ US healthcare providers from NPI Registry. Phone, taxonomy, CEO contact + Google-enriched website, reviews, emails.

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

## Pricing

from $1.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.

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 Registry API — Healthcare Provider Lookup & Enrichment

Search the U.S. NPI Registry (6M+ healthcare providers) and optionally enrich each provider with Google data: website, LinkedIn, social profiles, and secondary emails harvested from the provider's homepage.

### 📤 Output fields

- **NPI #** and enumeration type (individual / organization)
- **Provider name** (first + last + credential) or **organization name**
- **Authorized official** (CEO / Medical Director name, title, phone)
- **Primary taxonomy** (specialty code + description + license)
- **Location address** (line, city, state, ZIP, phone, fax)
- **Mailing address**
- **Status, enumeration date, last updated**
- **Google enrichment** *(optional, +2-4s/record)*: website, LinkedIn company page, Facebook page, secondary emails parsed from the website

| Field | Type | Description |
|-------|------|-------------|
| `npi` | string | 10-digit NPI number (unique identifier) |
| `enumerationType` | string | `NPI-1` (individual) or `NPI-2` (organization) |
| `organizationName` | string | Legal business name (NPI-2 only) |
| `firstName` / `lastName` / `credential` | string | Individual provider name (NPI-1 only) |
| `authorizedOfficial` | object | `{firstName, lastName, title, phone}` for organization contact |
| `primaryTaxonomy` | object | `{code, description, license, state}` — provider specialty |
| `locationAddress` | object | `{line1, line2, city, state, postalCode, phone, fax}` |
| `mailingAddress` | object | Same structure as `locationAddress` |
| `status` | string | `A` (active) or `D` (deactivated) |
| `enumerationDate` | string | ISO date the NPI was first issued |
| `lastUpdated` | string | ISO date of last record change at CMS |
| `enrichment.website` | string | Provider website (when Google enrichment is on) |
| `enrichment.linkedinUrl` | string | LinkedIn company page URL |
| `enrichment.facebookUrl` | string | Facebook page URL |
| `enrichment.secondaryEmails` | array | Emails parsed from the provider's homepage |

### 📥 Input

1. **Free-text search** — by city, state, ZIP, name, specialty (taxonomy).
2. **By NPI #** — look up specific 10-digit NPI numbers (bulk).

### 💻 Code examples

```json
{
  "searchMode": "search",
  "state": "TX",
  "city": "Dallas",
  "taxonomyDescription": "Dentist",
  "maxResults": 100,
  "enrichWithGoogle": true,
  "enrichLimit": 25
}
```

```json
{
  "npi": "1487344586",
  "enumerationType": "NPI-2",
  "organizationName": "1 FAMILY CLINIC INC",
  "authorizedOfficial": {
    "firstName": "MANEESH",
    "lastName": "SINGHAL",
    "title": "CEO/ Medical Director",
    "phone": "2132639095"
  },
  "primaryTaxonomy": {
    "code": "207QG0300X",
    "description": "Family Medicine, Geriatric Medicine"
  },
  "locationAddress": {
    "line1": "701 N ALVARADO ST STE B",
    "city": "LOS ANGELES",
    "state": "CA",
    "postalCode": "900264005",
    "phone": "213-263-9095"
  },
  "enrichment": {
    "website": "https://1familyclinic.com/",
    "linkedinUrl": "https://www.linkedin.com/company/1-family-clinic",
    "secondaryEmails": ["info@1familyclinic.com"]
  }
}
```

### 💵 Pricing

Pay-per-result. The free NPI Registry lookup is included; the Google enrichment step is charged per enriched record (each enrichment runs one SERP search + one website fetch).

### 🎯 Use cases

- MedTech and pharma B2B prospecting
- Healthcare staffing and locum tenens recruitment
- Insurance network discovery
- Telehealth platform onboarding
- Medical SaaS sales (EHR, RCM, scheduling)
- Provider directory enrichment and verification
- Local-SEO and reputation management for clinics

### Data source

This actor wraps the public **NPI Registry API** maintained by CMS (Centers for Medicare & Medicaid Services). Data is public-domain federal data. Optional enrichment uses publicly accessible search engine results and the provider's own public website.

# Actor input Schema

## `searchMode` (type: `string`):

How to query NPI Registry: by free-text search, or by specific NPI numbers.

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

List of 10-digit NPI numbers to look up. Used only when searchMode = byNpi.

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

Partial match on organization name. Used in search mode.

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

Provider first name (individual NPIs). Used in search mode.

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

Provider last name (individual NPIs). Used in search mode.

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

City of the provider's practice location.

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

US state abbreviation, e.g. CA, TX, NY.

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

US ZIP code of the provider's practice location.

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

Specialty keyword (e.g. "Dentist", "Family Medicine", "Pediatric").

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

NPI-1 = individual, NPI-2 = organization.

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

Hard cap on records to return (API pages 200 at a time).

## `enrichWithGoogle` (type: `boolean`):

For each provider, find website, LinkedIn, Facebook page, and secondary emails using a web search powered by an internal SERP fetcher. No API key required. Adds ~2-4s per provider.

## `enrichLimit` (type: `integer`):

Max number of providers to enrich. Capped to keep runtime bounded.

## `proxyConfig` (type: `object`):

Apify proxy for Google enrichment requests.

## Actor input object example

```json
{
  "searchMode": "search",
  "npiNumbers": [],
  "enumerationType": "",
  "maxResults": 200,
  "enrichWithGoogle": false,
  "enrichLimit": 50,
  "proxyConfig": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `providers` (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": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("makework36/npi-registry-api").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": [] }

# Run the Actor and wait for it to finish
run = client.actor("makework36/npi-registry-api").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": []
}' |
apify call makework36/npi-registry-api --silent --output-dataset

```

## MCP server setup

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

```

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/NUTJXgH2K7XfIH3CS/builds/vik2TvWKXhMuqP1ND/openapi.json