Health Provider API
doctor NPI API

Doctor NPI API for individual (NPI-1) records

Telehealth, scheduling, and credentialing flows need person-level fields, not organization envelopes.

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

Why teams choose Health Provider API

Telehealth, scheduling, and credentialing flows need person-level fields, not organization envelopes.

  • Structured name and credential fields for NPI-1
  • Primary taxonomy and license metadata
  • Same key and quota as organization lookups

Compare the official registry vs Health Provider API

Try the API
curl -sS -H "Authorization: Bearer YOUR_API_KEY" "https://healthproviderapi.com/api/v1/npi/1003000126"
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