Provider onboarding
NPI validation API for provider onboarding workflows
Confirm identifiers before you persist roster rows. One lookup returns normalized registry fields your enrollment services can trust—without implying licensure or credentialing checks.
Typical workflow
- Collect NPI (and optional display name/state) during clinician or facility signup.
- Call GET /api/v1/npi/{npi} from your backend with a dashboard API key.
- Branch on HTTP 200 vs 404 and map entity type, taxonomy, and status into your onboarding record.
- Optional: add ?enrichment=quality_freshness on Growth+ for completeness and freshness signals (2 credits).
What the API checks
- Ten-digit NPI format and registry lookup (existence vs npi_not_found)
- Entity type (NPI-1 individual vs NPI-2 organization)
- Primary taxonomy and practice addresses from NPPES
- Active vs deactivated registry status
Not verified by registry data alone
CMS NPI Registry data does not prove licensure, board certification, sanctions, or payer credentialing. Use your own credentialing and compliance processes for those decisions.
Input → output
Concrete API examples
Replace YOUR_API_KEY with a dashboard key. Full schemas live in OpenAPI.
Request (single NPI)
curl -sS -H "Authorization: Bearer YOUR_API_KEY" "https://healthproviderapi.com/api/v1/npi/1003000126"Response shape (illustrative)
{
"data": {
"npi": "1003000126",
"entityType": "NPI-1",
"status": "active",
"primaryTaxonomy": { "code": "207Q00000X", "description": "Family Medicine" }
},
"meta": { "requestId": "req_onboard01", "cached": true }
}