Product and engineering notes
For the API contract, see Documentation and the OpenAPI spec in the repository.
Check NPI format locally, then confirm against the official registry with a single HTTP call—without hand-parsing NPPES in your app.
A practical flow for calling the US NPI Registry from your backend: auth, lookup, errors, and when to add directory search.
Same registry data, different integration surface. When the free official API is enough—and when a wrapped API saves your team time.
Combine directory search, NPI lookup, and bulk refresh so member-facing search and nightly sync share one provider schema.
Use direct NPI lookup when you have the identifier; use directory search when you have names, locations, or taxonomy filters.
A ten-digit National Provider Identifier used in US healthcare claims and directories—and how developers validate it in products.
What NPI-1 and NPI-2 mean in plain language—before you wire registry fields into onboarding, directories, or billing screens.
Patient intake often needs a clinician NPI on file. Here is a small HTTP contract you can call from your stack instead of maintaining NPPES parsing in the telehealth path.
Engineering guide: which NPPES name and taxonomy fields to map for NPI-1 individuals vs NPI-2 organizations in your API client.
What “hit”, “miss”, and “stale” mean for your integration—and why they matter during upstream outages.
How monthly entitlements and per-key rate limits work together to protect the registry and your budget.
The public registry is authoritative but noisy. Here is how a thin API layer keeps integrations stable.