NPI Registry Scraper (US Healthcare Providers)

US doctors, dentists, therapists, clinics and other healthcare providers from the official NPPES NPI Registry run by CMS. For each provider: NPI number, name (individual or organization), credential, primary specialty and taxonomy code, license number and state, practice address with phone and fax, mailing address, status, enumeration and last-update dates, and — for organizations — the authorized official.

Uses the registry's public API. No login, no key, no browser, no proxy.

What it is for

• Healthcare lead lists — every dentist in a city, every family physician in a ZIP.
• Provider verification — check NPI numbers, specialties and licenses.
• Network and market mapping by specialty and area.

Input

{
  "searches": [
    {"specialty": "dentist", "city": "Austin", "state": "TX"},
    {"specialty": "family medicine", "postalCode": "10001"}
  ],
  "npiNumbers": ["1043458821"],
  "providerType": "any",
  "maxItems": 200
}

Search keys: specialty, firstName, lastName, organizationName, city, state, postalCode.

Four things worth knowing

1. At most 1,200 providers per search

The registry stops paging at 1,200 results. Past that it keeps returning the same 200 providers again rather than an error — a naive scraper repeats them. This Actor stops at the limit and marks the search possiblyTruncated when there may be more; split it by city or ZIP code to get everyone.

2. The registry never says how many matched

Its count field is only the size of each response. So the only honest signal of a cut-off is a full last page — that's what the truncation flag reports.

3. The first address isn't always the practice

Each provider has a mailing and a practice ("location") address, and their order varies — the practice came first for only about 1 in 5 providers. The Actor returns them as practiceAddress and mailingAddress, never "address 1".

4. Errors come back looking like success

A misspelled specialty or a state on its own is answered normally, with an error message inside. The Actor turns that into an error row with the registry's own wording (e.g. "No taxonomy codes found with entered description").

ZIP codes are formatted as 78746-7759 (the registry sends 787467759).

Output

{
  "recordType": "PROVIDER",
  "npi": "1154494250",
  "providerType": "organization",
  "name": "360 DENTAL CARE P.A.",
  "primarySpecialty": "Dentist, General Practice",
  "licenseNumber": "16292",
  "practiceAddress": {
    "line1": "3660 STONERIDGE RD STE B101", "city": "AUSTIN", "state": "TX",
    "postalCode": "78746-7759", "phone": "512-327-3631", "fax": "512-327-2234"
  },
  "registryUrl": "https://npiregistry.cms.hhs.gov/provider-view/1154494250"
}

Every row also carries the registry's complete record (all taxonomies, identifiers, other names, practice locations, endpoints).