Directory maintenance
Provider directory sync from the NPI Registry
Keep member-facing directories and internal rosters aligned with NPPES: discover providers by name, confirm by NPI, and reconcile batches on a schedule.
Typical workflow
- Expose directory search behind your UI for unknown identifiers.
- Persist NPI and requestId on each row after lookup or bulk refresh.
- Schedule bulk jobs to refresh stale rows; use enrichment freshness bands where helpful.
- Plan for change monitoring as a follow-up capability—do not promise webhook alerts today.
What the API checks
- GET /api/v1/providers/search for in-app search and typeahead
- GET /api/v1/npi/{npi} when the NPI is already known
- POST /api/v1/npi/bulk for nightly reconciliation jobs (up to 50 NPIs per call)
- Freshness and completeness enrichment on single lookup/search (Growth+)
Not verified by registry data alone
Automated change detection and outbound webhooks are not shipped yet (see product roadmap). Position directory maintenance on search + bulk + enrichment until monitoring APIs land.
Input → output
Concrete API examples
Replace YOUR_API_KEY with a dashboard key. Full schemas live in OpenAPI.
Directory search
curl -sS -H "Authorization: Bearer YOUR_API_KEY" "https://healthproviderapi.com/api/v1/providers/search?last_name=Smith&limit=10"Bulk reconciliation
curl -sS \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"npis":["1003000126","1932100864","1851789159"]}' \
"https://healthproviderapi.com/api/v1/npi/bulk"