provider directory API

Provider directory API on NPI registry data

Sync directories, power in-app search, and validate roster rows without owning NPPES normalization.

No credit card on free tierOpenAPI specPostman collectionUS NPI Registry (NPPES) source dataNPI-1 and NPI-2

Why teams choose Health Provider API

Sync directories, power in-app search, and validate roster rows without owning NPPES normalization.

  • Lookup known NPIs; search when identifiers are missing
  • POST /api/v1/npi/bulk for batch reconciliation jobs
  • Response metadata for cache hits and support traces

Compare the official registry vs Health Provider API

Try the API
curl -sS -H "Authorization: Bearer YOUR_API_KEY" "https://healthproviderapi.com/api/v1/providers/search?last_name=Smith&limit=10"
Quickstart in the docs

Same registry, better integration surface

Authoritative NPPES data with predictable JSON, auth, and operational headers—so engineering can ship features instead of parsers.

Start free — no credit card