# NPI Registry Scraper - Healthcare Provider Leads Export US healthcare providers by specialty and location from the official NPPES NPI registry. Street address on every row, phone and fax where registered. Smart geo match keeps every lead in your target area. CSV/JSON. Canonical product page: https://mayd-it.com/data-tools/actors/us-healthcare-providers-scraper/ Public Actor: https://apify.com/maydit/us-healthcare-providers-scraper ## Example input ```json { "providerType": "individual", "specialty": "Cardiovascular Disease", "state": "CA", "maxResults": 10 } ``` ## Full guide ![Explore registered care providers — illustrative workflow](https://api.apify.com/v2/key-value-stores/YGxD9JRpduom8Q5Zd/records/us-healthcare-providers-scraper-49166d2eb8ed.png?signature=J9GoxFYYrhrdx27xX74y) ## Explore registered care providers For healthcare market research and provider-directory work, build a focused list from the official NPPES NPI registry. **Coverage:** Individual and organization records from NPPES. Phone and fax availability depends on what each provider registered. [Open this Actor in Console](https://console.apify.com/actors/hMH1cnGaYHalRZ3rr/input) · [First run](#try-this-actor) · [Results](#result-preview) · [Cost](#usage-and-pricing) · [Full guide](#full-guide) ## Try this Actor 1. Choose a specialty description from the existing examples and pair it with a city/state or full ZIP. Lower the maximum provider count for the first run. 2. Review the run's dataset and NPI record links. Read `SUMMARY` for time or spending stops before expanding the geography. **Read the results correctly:** A query can return at most 1,200 providers. The matched address may be a mailing address; registry presence is not a verification of current practice activity. ## Result preview The dataset view highlights these columns: - **NPI** · `npi` - **Provider category** · `providerType` - **Registered name** · `name` - **Registered credentials** · `credential` - **Primary specialty** · `primarySpecialty` - **Matched registered address** · `address1` Use the original source links and the field definitions below when interpreting the results. CSV works well for flat columns; JSON preserves nested values. ## Usage and pricing Base result rate on the FREE tier: **$2 per 1,000 results**. The [Pricing tab](https://apify.com/maydit/us-healthcare-providers-scraper/pricing) shows your plan's result rate and any Actor Start charge. Set a small result limit for the first run; the requested limit is not a guarantee of that many results. --- ## Full guide > Pull a clean, geo-targeted list of US doctors, dentists, clinics, and organizations straight from the official CMS NPPES NPI registry - a street address on every row, plus phone and fax wherever the provider registered them. ### What it does This NPI registry scraper turns the official CMS NPPES NPI registry into a lead-gen-ready dataset. Query US healthcare providers by specialty, name, city, state, or postal code, and export a healthcare provider database to CSV or JSON in minutes. Unlike a raw NPPES NPI registry API dump that returns dozens of credentialing fields, this actor uses **smart address matching**: records whose selected registered address does not match your target geography are dropped. A matching registered address may be a mailing address; it does not verify a current practice location or activity. Each record includes the provider's NPI number, name, credential, primary and full specialty list, phone, fax, and street address - the fields sales, recruiting, and market-research teams actually use. ### Who it's for - **Healthcare sales & lead generation** teams building targeted provider call lists - **Medical-device and pharma reps** prospecting by specialty and territory - **Healthcare recruiters** sourcing physicians, NPs, and specialists by location - **Market research & analytics** teams mapping provider density by city or ZIP - **Health-tech and SaaS** companies enriching or building a provider directory ### What you get (output) Every row is one provider (individual or organization) with these fields: | Field | Description | |---|---| | `npi` | 10-digit National Provider Identifier | | `providerType` | Individual (NPI-1) or Organization (NPI-2) | | `name` | Provider or organization name | | `credential` | Credential(s), e.g. MD, DO, DDS, NP | | `gender` | Provider sex as recorded in NPPES: `M` or `F` (individuals only; empty for organizations and for the rare individual with none on file) | | `primarySpecialty` | Primary specialty / taxonomy description | | `taxonomyCode` | Primary NUCC taxonomy code | | `allSpecialties` | Full list of the provider's specialties | | `address1` | Street address - a practice location in your target area when the provider has one there, otherwise the mailing address that matched (with no location filter: the practice location) | | `address2` | Suite / unit line, when present | | `city` | City | | `state` | State | | `postalCode` | ZIP / postal code | | `phone` | Practice phone number | | `fax` | Practice fax number | | `soleProprietor` | Sole-proprietor flag (individuals) | | `enumerationDate` | Date the NPI was issued | | `lastUpdated` | Date the provider's NPPES record was last updated | | `npiUrl` | Direct link to the provider's NPPES record | | `scrapedAt` | When this actor fetched the row | ### Input / how to query Filter the NPI registry by any combination of: - **Provider type** - individual providers (NPI-1) or organizations (NPI-2) - **Specialty / taxonomy** - target by taxonomy description, e.g. `Dermatology` or `Nurse Practitioner` (NPPES does not accept NUCC taxonomy codes such as `207N00000X` as a search term, but every row returns the provider's `taxonomyCode`) - **Name** - provider or organization name - **City** - narrow to a single city - **State** - narrow to one state. NPPES refuses a state on its own, so pair it with a specialty, city, ZIP or name - **Postal code** - drill down to a specific ZIP - **Max run seconds** - wall-clock budget for the run (default 240). The NPI Registry can stall for half a minute per page; when the budget is reached the Actor stops cleanly and finishes successfully with the providers it already has, and records `stoppedEarlyOnTimeLimit: true` in the run's `SUMMARY` If NPPES refuses a search (a state with nothing else, a taxonomy code instead of a description, or an organization name with Provider type set to Individual), the run fails with NPPES's own error message instead of returning an empty dataset. The NPPES API returns at most 1,200 providers per search, so split large areas by city or ZIP. Set your location filters and **smart address matching** removes any provider whose registered address falls outside the target geo, so you never have to clean out-of-area rows by hand. Results export as CSV, Excel, or JSON. ### Example use cases - **Medical-device territory list** - export the orthopedic surgeons in each ZIP code of a territory (one run per ZIP) with phone and address, ready for the field team. - **Pharma specialty targeting** - pull cardiologists (specialty `Cardiovascular Disease`) in a state for a sample-drop campaign, splitting big states by city to stay under the 1,200-per-search cap. - **Recruiter sourcing** - build a list of nurse practitioners in a metro area, complete with practice contact details. - **Dental / clinic outreach** - generate a dentist and clinic lead list for a region, with fax and phone for direct outreach. - **Market sizing** - count and map provider density for a specialty city by city or ZIP by ZIP to prioritize expansion. ### Recurring use & scheduling The NPPES NPI registry is refreshed by CMS on a regular cycle as providers are added and updated. Use Apify **Schedules** to re-run this actor weekly or monthly and keep your provider database current. Point the run at the same dataset and dedupe on the `npi` field (the NPI is unique per provider) so repeated runs surface only new or changed records instead of duplicates - ideal for ongoing lead monitoring by specialty or territory. ### FAQ #### How do I download a list of doctors by specialty and location? Set the specialty filter (a taxonomy description such as `Dermatology`) plus a city, state, or postal code, then run the actor. It returns the matching providers with contact details - up to 1,200 per search, the NPPES API limit - ready to export to CSV, Excel, or JSON. #### How do I export NPI registry data to CSV or Excel? Every run produces a structured dataset you can download as CSV, Excel, or JSON directly from the run's Storage tab, or pull via the Apify API. #### Where can I get healthcare provider phone numbers and addresses for sales? This actor sources them from the official CMS NPPES NPI registry. Each row includes the provider's registered street address (`address1`, `city`, `state`, `postalCode`) plus `phone` and `fax` wherever the provider registered them, so your list is contact-ready. #### Is there a free NPPES NPI registry API without a key? The underlying CMS NPPES data is public and this actor reads it without any API key on your part. You run it on Apify and get a clean, filtered dataset instead of raw API pagination. #### How do I build a physician mailing list by state? Filter by state plus a specialty (NPPES refuses a state on its own), run the actor, and export the results; add a city or ZIP to go past the 1,200-per-search cap in large states. Each row carries the provider's name, credential, and full street address for direct mail. #### How can I find providers by specialty in a specific ZIP? Combine the specialty filter with a postal code. Smart address matching drops any provider outside that ZIP, so the export contains only in-area providers. #### How do I get NPI data for individual vs organization providers? Use the provider-type filter: NPI-1 for individual providers, NPI-2 for organizations. The `providerType` field in the output labels each row so you can split or segment them. #### Is scraping the CMS NPI registry legal? The NPPES NPI registry is published by CMS as public data specifically for lookups and downloads. This actor reads that public information; as always, ensure your outreach complies with applicable marketing and privacy regulations. #### How often is the NPPES NPI registry updated? CMS updates NPPES regularly as providers enroll and revise their records. Schedule this actor to re-run on your preferred cadence to keep your dataset in sync. ### Data source & notes - **Source:** Official CMS NPPES NPI Registry (National Plan and Provider Enumeration System) - public US government data, no API key required. - **Coverage:** US individual providers (NPI-1) and organizations (NPI-2). - **Fields:** Only the fields listed in the output table above are returned - this actor deliberately delivers the lead-relevant subset rather than every raw credentialing field. - **Geo accuracy:** Smart address matching keeps results inside your specified location, so no manual cleanup of out-of-area rows. - **Compliance:** Data is public, but you are responsible for using it in line with applicable marketing, calling, and privacy laws. ### Related actors Part of a set of US public-records tools that work well together: - [FDA Adverse Events Scraper](https://apify.com/maydit/us-fda-adverse-events-scraper) - device and drug safety reports for the same market - [FDA Recalls Scraper](https://apify.com/maydit/us-fda-recalls-scraper) - recall monitoring for medical products See the full collection at [apify.com/maydit](https://apify.com/maydit). ### Found this useful? If this actor saved you time, a short review on the Apify Store genuinely helps. Reviews are how the next person decides whether a tool is worth trying. Something broken, missing a field, or a source you want covered? Open an issue on the **Issues** tab and it will get looked at - that is the fastest route to getting it changed. #### Run spending limits The run stops at its spending limit. `SUMMARY.datasetItemsSaved` reports the number of rows actually saved, and `SUMMARY.stoppedOnChargeLimit` identifies this stop. A final batch may be saved only in part; increase the spending limit to collect more results. ## Help with your run Open the **Issues** tab on this Actor with the run URL, the input field that caused trouble and what you expected to receive. Remove API keys and private information before posting. [Explore more Mayd-It Actors](https://apify.com/maydit) ## Understand your run Open **Run report** in the run’s Output tab for saved-record counts, reported source issues and limits, and suggested next steps. Use **CSV export** to take the saved results into a spreadsheet. The existing JSON results and detailed machine-readable summary remain available. The report reflects this run’s recorded coverage. A successful run or a saved result does not establish that every possible source record was collected.