NPI Provider Registry Scraper — Specialty & Address
DeprecatedPricing
from $20.00 / 1,000 api queries
NPI Provider Registry Scraper — Specialty & Address
DeprecatedStructured NPPES/NPI feed of U.S. healthcare providers: name, taxonomy/specialty, practice address, and enumeration data. For health-tech, provider-directory and sales-intelligence teams. Statutory sources that don't break.
Pricing
from $20.00 / 1,000 api queries
Rating
0.0
(0)
Developer
K O
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
22 days ago
Last modified
Categories
Share
CMS NPI Healthcare Provider Registry Tracker – NPPES Provider API
A CMS NPI Registry API wrapper and healthcare-provider data feed that pulls U.S. providers from the official NPPES registry and normalizes each into a clean record: NPI, name (individual or organization), primary taxonomy/specialty, practice address, license state, phone and status. Use it to build a provider-directory dataset, a healthcare sales-intelligence feed, a credentialing lookup, or referral-network tooling.
Who uses it
Health-tech and provider-directory products, medical-device and pharma sales teams building territory lists, credentialing and payer-enrollment teams, and healthcare data vendors.
Why this is worth charging for
The NPI registry is the authoritative directory of U.S. providers, but its API returns deeply nested basic/address/taxonomy objects and caps skip at 1,000. This actor picks the practice-location address and primary taxonomy, handles enumeration type (individual vs organization), and delivers a clean, queryable provider feed by specialty, name or geography.
Output
Each dataset item is one normalized record:
{"npi": "1234567890","enumerationType": "NPI-1","name": "JOHN SMITH","credential": "MD","primaryTaxonomy": "Internal Medicine","taxonomyCode": "207R00000X","licenseState": "MA","addressCity": "BOSTON","addressState": "MA","addressPostal": "02118","phone": "617-555-1212","status": "A","url": "https://npiregistry.cms.hhs.gov/provider-view/1234567890","source": "CMS NPPES"}
Input
| Field | Description |
|---|---|
enumerationType | Restrict to individual or organizational providers. |
taxonomyDescription | Specialty description, e.g. 'Cardiology' or 'Pharmacy'. |
organizationName | Organization name search (supports trailing wildcard). |
firstName | Individual provider first name. |
lastName | Individual provider last name. |
city | Practice city. |
state | Practice state. |
postalCode | Practice ZIP (supports wildcard). |
npi | Look up one specific NPI number. |
pageSize | Results per page (NPPES max 200). |
maxPagesToScan | Pages per run (NPPES caps total skip at 1,000). |
onlyNewSinceLastRun | Recommended for schedules — skips records already returned by a previous run using persisted state, so you're only charged for genuinely new items. |
maxItems | Stop after this many normalized records. |
Pricing (Pay-Per-Event)
query— $0.02, charged once per run for the API query/poll.provider-record— $0.01 per normalized record pushed. This is the primary event.apify-actor-start(Apify-managed) — covers baseline compute per run.
A specialty+geography pull returns up to ~1,000 providers per run for a few dollars. Narrow with city/state/taxonomy to build precise territory lists cheaply.
Source & reliability
Data comes from the official npiregistry.cms.hhs.gov NPPES API. Practice-location address and primary taxonomy are selected automatically. No key or proxies required. Run npm test for the offline self-test covering the normalizer, including edge cases and missing-field handling.
FAQ
Is there an API for the NPI registry?
Yes — this actor wraps the official NPPES API and returns clean, flattened provider records via the Apify API, webhook or export.
Can I build a specialty list for a state?
Yes. Set taxonomyDescription and state (NPPES caps results at 1,200 per query; narrow by city/ZIP for more coverage).
Need the rest of the record on these companies?
This actor returns one source. KYB Company Data Enrichment takes a company name and returns what the public record says about it across up to nine sources — state business registries, UCC lien filings, tax warrants and WARN layoff notices, the FMCSA motor-carrier census, the CMS NPI Registry, USAspending federal awards, EPA ECHO compliance, SEC EDGAR filings and CourtListener federal dockets.
Every enriched field carries its source and its match confidence. Only matches above the accept threshold are merged — anything weaker is surfaced as a suggestion and never folded into the record, because a false join is worse than returning nothing.
SEO keywords: NPI registry API, NPPES API, healthcare provider data, physician directory scraper, provider lookup API, medical sales territory data