Live
Service status
Check live service health and documented failure responses before you integrate.
Identity & Verification
NPI lookup and healthcare provider verification API
Verify doctors, clinics and other healthcare providers during credentialing, claims and onboarding. Look up an NPI in the official registry, compare a name, state and specialty with the record, or search providers by name and location.
Category
Identity & Verification
Endpoints
1
Key Features
4
Frequently asked questions
4
Used by people at these companies
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI
API artifacts
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
API keys
Protected access
Authenticated endpoints use API keys with clear credit costs before you call them.
10,000
Free allowance
Start with 10,000 monthly credits and upgrade only when usage grows.
What this API helps you ship
Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.
Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.
Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.
Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.
Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.
Integration workflow
A simple path from first request to repeatable production usage.
Authenticate once
Send your API key with the documented header and keep requests consistent across services.
Query with examples
Start from the curl and HTTP samples, then map the parameters into your application code.
Operate and monitor
Use status codes, credit costs, and response fields to build retries, logs, and alerts.
Developer kit
Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.
OpenAPI schema
Generate clients or inspect every request and response shape.
Postman collectionImport ready-made requests for manual testing and team handoff.
SDKs and CLIUse maintained packages and command-line workflows instead of writing boilerplate.
MCP integrationExpose domain intelligence to AI agents and internal assistant workflows.
Parameters and response map
Scan the inputs, output fields, and status codes before wiring the endpoint into your client.
Parameter
numbernamestatetaxonomy
Example response
npistatuschecksum_validproviderprovider.typeprovider.nameprovider.activeprovider.primary_taxonomyprovider.primary_taxonomy.codeprovider.primary_taxonomy.descriptionprovider.primary_taxonomy.stateprovider.primary_taxonomy.license
HTTP status codes
200400401402429
Endpoints
GET
/v1/npi
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Live
Service status
Check live service health and documented failure responses before you integrate.
OpenAPI
API artifacts
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
API keys
Protected access
Authenticated endpoints use API keys with clear credit costs before you call them.
10,000
Free allowance
Start with 10,000 monthly credits and upgrade only when usage grows.
Key Features
Official registry record
The current record from the official US NPI registry: individual or organization, credentials, enumeration and update dates, and status.
Specialties and licenses
Every taxonomy with its license number and state, practice locations, mailing address, other identifiers and former names.
One verified answer
Send a name, state and specialty to compare. Verified is true only when the provider is active and every detail you sent matches.
Search by name
Find providers by individual or organization name with city, state, ZIP code and specialty filters, up to 50 per page.
Example request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/npi?number=1003000126&state=MD"Example response
{
"npi": "1003000126",
"status": "found",
"checksum_valid": true,
"provider": {
"type": "individual",
"name": "ARDALAN ENKESHAFI",
"active": true,
"primary_taxonomy": { "code": "208M00000X", "description": "Hospitalist", "state": "DC", "license": "MD600003480" },
"addresses": { "location": { "city": "BETHESDA", "state": "MD" } }
},
"verification": {
"state": { "status": "match", "matched_on": "location" },
"verified": true
}
}Frequently asked questions
What happens with a mistyped NPI?
Every NPI has a check digit. A number that fails it is reported as not valid straight away, without a registry search.
What does not_found mean?
The number is well formed but the registry has no active record for it. Deactivated numbers are not listed by the registry.
What if the registry is unavailable?
The result is unknown with the reason, never not found, and the request is refunded.
How many credits does it cost?
One credit per lookup or search page. Unknown results are refunded.
Related tools and resources
HTTP status codes
These are the HTTP status codes to handle, so you can tell apart successful responses, auth issues, credits, rate limits, missing data, and upstream failures.
OK
200
Request successful
Bad Request
400
Invalid parameters
Unauthorized
401
Missing or invalid API key/session.
Payment Required
402
Not enough credits to run this request.
Too Many Requests
429
Rate limit exceeded
Look up an NPI