US provider lookups by NPI, built for developers

NPI API wraps the public CMS NPPES NPI Registry behind a clean REST API: bearer API keys, normalized JSON, caching, and usage-aware billing so you ship faster than wiring upstream responses yourself.

Read the docs View pricing

Who it is for

Teams that need reliable NPI-1 and NPI-2 data in applications—credentialing workflows, billing support tooling, directory products, and internal ops—without maintaining their own NPPES client, cache, and normalization layer.

Why not call NPPES directly?

Normalized response shape documented in OpenAPI, consistent across lookups.
Authentication, quotas, and request logging designed for product integrations.
Cache-friendly behavior so you are not re-parsing large upstream payloads every time.

Get started in minutes

Create an account and an API key from the dashboard (available after auth is enabled).
Call GET /api/v1/npi/{npi} with your key.
Handle documented success and error responses in your stack.

Open the full quick start →

Sample response (illustrative)

{
  "data": {
    "npi": "1003000126",
    "entityType": "NPI-1",
    "status": "active",
    "name": { "full": "…", "first": "…", "last": "…" },
    "primaryTaxonomy": { "code": "208M00000X", "description": "…" }
  },
  "meta": { "requestId": "req_…", "cached": true }
}

Exact fields follow the published OpenAPI contract.

Typical use cases

Enrich internal tools with provider identity and taxonomy context.
Validate or pre-fill NPI fields before deeper verification workflows.
Power customer-facing lookups where NPPES is the source of truth.

Pricing preview

Free and paid tiers scale by monthly lookup quota and API key limits. Compare plans →

FAQ

Is this a replacement for legal or clinical verification? No. Data comes from the public NPI Registry; you remain responsible for compliance in your domain.

Do you sell provider data beyond what NPPES exposes? No. The product packages registry access with API ergonomics, not expanded clinical datasets.