NPI / NPPES Healthcare Provider Registry Lookup

Search the official US NPI Registry (npiregistry.cms.hhs.gov) — 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) — 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.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.