NPI Registry Scraper — US Healthcare Provider Data (NPPES)

This NPI Registry scraper extracts US healthcare provider data from the official NPPES NPI Registry maintained by the Centers for Medicare & Medicaid Services (CMS). Use it to pull provider name, NPI number, specialty/taxonomy, license number, full address, phone and fax across 8M+ doctors, dentists, pharmacies, clinics and hospitals — with no API key, no login and no blocking.

It reads the official government API, so the data is authoritative and never throttled by anti-bot walls. One run can return tens of thousands of provider records filtered by state, specialty, city and provider type, then export to CSV, JSON or Excel.

What you get

Each provider is one structured dataset item. Output fields:

Field	Description
npi	10-digit National Provider Identifier.
enumerationType	NPI-1 (individual) or NPI-2 (organization).
organizationName	Organization name (for NPI-2 providers).
firstName	Provider first name (for NPI-1 providers).
lastName	Provider last name (for NPI-1 providers).
credential	Credential (e.g. MD, DDS, RN).
gender	Provider gender.
soleProprietor	Sole proprietor status.
status	NPI record status (active / deactivated).
authorizedOfficialName	Name of the organization's authorized official.
authorizedOfficialTitle	Title of the authorized official.
authorizedOfficialPhone	Phone of the authorized official.
primaryTaxonomy	Primary taxonomy / specialty description.
taxonomyCode	Taxonomy code.
taxonomyGroup	Taxonomy group.
licenseNumber	State license number.
addressLine	Practice street address.
city	City.
state	State code.
postalCode	ZIP / postal code.
phone	Practice phone number.
fax	Practice fax number.
enumerationDate	Date the NPI was issued.
lastUpdated	Date the record was last updated.
scrapedAt	Scrape timestamp (ISO 8601).

Export every field to JSON, CSV, Excel or XML, or pull via the Apify API.

Example output

{
  "npi": "1234567890",
  "enumerationType": "NPI-1",
  "firstName": "Jane",
  "lastName": "Doe",
  "credential": "DDS",
  "primaryTaxonomy": "Dentist",
  "licenseNumber": "DEN-00123",
  "addressLine": "123 Main St, Suite 4",
  "city": "Brooklyn",
  "state": "NY",
  "postalCode": "11201",
  "phone": "718-555-0100",
  "status": "A",
  "lastUpdated": "2026-05-01",
  "scrapedAt": "2026-05-15T08:30:00.000Z"
}

Use cases

• Medical & pharma sales — build targeted prospect lists of providers by specialty, state and city.
• Healthcare marketing — reach dentists, physicians, clinics and pharmacies at scale with verified contact data.
• Recruitment & staffing — source healthcare professionals nationwide by specialty and location.
• Research & analytics — map provider density, specialty distribution and licensing across the US.
• CRM enrichment & verification — verify NPI numbers, licenses and active status against the official registry.

How to use

1. Click Try for free / Run on the Actor page (or call it via the Apify API).
2. Choose states (any combination of US state codes, or all 50 + DC by default).
3. Filter by taxonomyDescription (specialty), enumerationType (individual / organization) and city.
4. Set maxRecords to cap the run, or 0 for all matching, then export to CSV, JSON or Excel.

Input fields

Field	Type	Description
states	array	US state codes to scrape (e.g. NY, CA, TX). Defaults to all 50 states + DC.
taxonomyDescription	string	Filter by provider specialty (e.g. dentist, pharmacy, nurse practitioner). Leave empty for all.
enumerationType	string	Provider type: NPI-1 = individuals, NPI-2 = organizations, empty = both.
city	string	Optional city filter (e.g. Brooklyn). Leave empty for the whole state.
maxRecords	integer	Maximum providers to save. 0 = all matching records.

Example input

{
  "states": ["NY", "CA", "TX"],
  "taxonomyDescription": "dentist",
  "enumerationType": "NPI-1",
  "city": "",
  "maxRecords": 10000
}

FAQ

Is it legal to scrape the NPI Registry?

Yes. The NPPES NPI Registry is a public dataset published by CMS specifically for public use, and the Actor reads the official government API. You remain responsible for using contact data in compliance with laws such as CAN-SPAM and TCPA.

Do I need an API key or a login?

No. There is no NPPES account, login or API key required — you only need an Apify account to run the Actor.

How much data can I get?

The registry contains 8M+ providers. A single run can return tens of thousands of records — set maxRecords to 0 to capture all matching providers across your selected states.

How fresh is the data?

The NPPES NPI Registry is updated daily by CMS, and the Actor pulls live data at run time. Schedule it to keep your provider database always current.

What output formats are supported?

Results are stored in a structured Apify dataset and can be exported as JSON, CSV, Excel or XML, or accessed via the Apify API.

Is this an NPPES NPI Registry API alternative?

Yes. It reads the official CMS government API for you and turns it into a ready-to-use dataset, so it works as an unofficial NPPES API alternative without any account, API key or login.

How do I export NPI data to CSV or JSON?

Run the Actor, then download the results from the dataset as CSV, JSON, Excel or XML — a simple way to bulk export NPI numbers and healthcare provider records to CSV.

Can I scrape doctor and provider data without an API key?

Yes. This NPI number scraper pulls US healthcare provider data with no API key and no login — just an Apify account to run it.

Scheduling & integration

Schedule this Actor on Apify to keep an always-fresh US healthcare provider database. Export results to JSON, CSV or Excel, sync to Google Sheets, or push to your CRM, database and webhooks through the Apify API.

---

Changelog

2026-06-07

• Docs: added coverage for NPPES API alternative usage, exporting NPI data to CSV/JSON, and scraping healthcare provider data without an API key.

2026-06-05

• 🛡️ Reliability fix: results are no longer dropped by strict output validation — runs now complete cleanly even at high volume (thousands of results).
• ⚡ Stability & performance hardening; fresh rebuild.

• 2026-06-01 — Maintenance & reliability pass: pulled the latest source and rebuilt the Actor on the current base image; build verified.

• 2026-05-25 — Maintenance & reliability pass: pulled the latest source and rebuilt the Actor on the current base image; build verified.

• 2026-05-20 — Maintenance pass: reviewed the input schema and default values for a smooth one-click start, and rebuilt the Actor on the latest base image.

2026-06-04

• Verified live & refreshed build — reliability/maintenance pass.