# US NPPES NPI Healthcare & Senior Care Provider API (`lumenfetch/nppes-npi-healthcare-provider-registry-api`) Actor

Queries the official US HHS CMS National Plan and Provider Enumeration System (NPPES NPI Registry API v2.1) for licensed medical practices, nursing facilities, home health agencies, and specialists with verified TLS.

- **URL**: https://apify.com/lumenfetch/nppes-npi-healthcare-provider-registry-api.md
- **Developed by:** [Lumenfetch](https://apify.com/lumenfetch) (community)
- **Categories:** Lead generation, Open source
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $9.00 / 1,000 extracted result items

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

## US NPPES NPI Healthcare & Senior Care Provider Registry API (`npiregistry.cms.hhs.gov`)

Queries the official **US Department of Health & Human Services (HHS) / Centers for Medicare & Medicaid Services (CMS) NPPES NPI Registry REST API v2.1** (`https://npiregistry.cms.hhs.gov/api/?version=2.1`) to retrieve active National Provider Identifier (NPI) records for healthcare organizations, home-health agencies, skilled nursing facilities, hospices, and individual practitioners.

#### Engineering & Compliance Guarantees

- **Verified TLS:** Uses `ssl.create_default_context()`.
- **Zero Synthetic Fallback Data:** If the CMS NPPES API is unreachable, the Actor exits with a non-zero exit code (`sys.exit(1)`) so you are never billed for placeholder rows.
- **Public Domain Federal Data (17 U.S.C. § 105):** Sourced directly from the official CMS NPPES Public API. Maintained by **Atelier Systems**.

# Actor input Schema

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

Specialty or facility type (e.g., 'Home Health', 'Skilled Nursing Facility', 'Hospice', 'Internal Medicine', 'Physical Therapist', 'Dentist').

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

Two-letter state filter (e.g., FL, TX, CA, NY, PA).

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

Optional city name.

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

Maximum number of verified NPI records to return (1 to 200).

## Actor input object example

```json
{
  "taxonomyDescription": "Home Health",
  "state": "FL",
  "city": "",
  "maxItems": 15
}
```

# Actor output Schema

## `dataset` (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 = {
    "taxonomyDescription": "Home Health",
    "state": "FL"
};

// Run the Actor and wait for it to finish
const run = await client.actor("lumenfetch/nppes-npi-healthcare-provider-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 = {
    "taxonomyDescription": "Home Health",
    "state": "FL",
}

# Run the Actor and wait for it to finish
run = client.actor("lumenfetch/nppes-npi-healthcare-provider-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 '{
  "taxonomyDescription": "Home Health",
  "state": "FL"
}' |
apify call lumenfetch/nppes-npi-healthcare-provider-registry-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lumenfetch/nppes-npi-healthcare-provider-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/7tJwmo7iAAqLi3gT1/builds/MrQbgm0yK3upgQhfO/openapi.json