Healthcare Provider Verification — NPPES/NPI
Verify a healthcare provider's NPI registration status, specialty (taxonomy), and practice location from CMS's free official NPPES registry. Covers both individual and organization NPIs. No key required.
Healthcare Provider Verification — NPPES/NPI returns 17 documented output fields, including matchedQuery, npi, enumerationType, name and isOrganization. Every field carries a declared type, a written description and an example value. 41 runs are recorded on Apify.
- 17
- Output fields
- 2
- Inputs
- 41
- Runs
- 2026-10-16
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| matchedQuery | stringnull | The query this row matched. | amazon product scraper |
| npi | stringnull | National Provider Identifier. | <npi> |
| enumerationType | stringnull | How the identifier was assigned. | <enumerationType> |
| name | stringnull | Display name as the source writes it. | Bitcoin |
| isOrganization | booleannull | Whether the address belongs to an organisation rather than a person. | true |
| status | stringnull | Outcome recorded for this row. | ok |
| isActive | booleannull | Whether the record is still active at the source. | true |
| credential | stringnull | Credential this row describes. | <credential> |
| primarySpecialty | stringnull | Primary Specialty as recorded for this row. | <primarySpecialty> |
| licenseNumber | stringnull | Licence number. | <licenseNumber> |
| licenseState | stringnull | State that issued the licence. | <licenseState> |
| practiceCity | stringnull | City where the practice is located. | <practiceCity> |
| practiceState | stringnull | State where the practice is located. | <practiceState> |
| practicePhone | stringnull | Phone number for the practice. | <practicePhone> |
| enumerationDate | stringnull | Date the identifier was assigned. | <enumerationDate> |
| lastUpdated | stringnull | ISO 8601 timestamp of the last change seen. | <lastUpdated> |
| verdict | stringnull | The Actor's conclusion for this row, stated in words. | pass |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"matchedQuery": "amazon product scraper",
"npi": "<npi>",
"enumerationType": "<enumerationType>",
"name": "Bitcoin",
"isOrganization": true,
"status": "ok",
"isActive": true,
"credential": "<credential>"
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| providers | arrayrequired | Providers to look up, each with npi, organizationName, or firstName/lastName (state optional to narrow). Example: [{"npi": "1063837144"}] or [{"organizationName": "Mayo Clinic"}] |
| maxResultsPerQuery | integeroptional | How many matching providers to return per query. |
04 — run
Run Healthcare Provider Verification on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
17 of 17 fields described
- What does Healthcare Provider Verification — NPPES/NPI return?
- It returns 17 documented output fields: matchedQuery, npi, enumerationType, name, isOrganization, status, isActive, credential, primarySpecialty, licenseNumber, licenseState and practiceCity. Each field declares its type, a description of what it holds, and an example value. The remaining 5 are listed in the output schema below.
- What input does Healthcare Provider Verification — NPPES/NPI require?
- providers is required. A further 1 input is optional. The full input schema, with types and defaults, is below.
- Does Healthcare Provider Verification — NPPES/NPI need an API key or login?
- No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
- How do I run Healthcare Provider Verification — NPPES/NPI?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.