Send the NPIs from your CRM, claims data or a registry export to the Dmand AI API and get back a verified professional or personal email and a mobile number for each physician, nurse practitioner or other provider it can reach. Each result comes back ready to write to your own records.
Illustration: four placeholder NPIs for invented providers return a professional email, a mobile number, a personal email and one not found.
Customers
Teams selling into US healthcare use Dmand AI
Circle Health · G2 review
I like Dmand AI’s extremely curated and comprehensive healthcare database, which you won’t find on any other platform with this level of detail.
NextDimension AI · G2 review
It’s like having a hyper-personalized mail writer that’s unbelievably efficient.
What the API returns
Dmand AI's NPI contact enrichment API takes a Type 1 NPI, the identifier CMS gives each individual provider, and returns the provider's professional or personal email and mobile number, or a not-found status. Emails come back only if they were validated in the last 30 days. It covers physicians, nurse practitioners, physician assistants and other NPI holders; executives and people without an NPI are outside its scope for now.
NPIs per bulk request
Up to 45 NPIs in one bulk request, or one at a time.Read the API docsBetter healthcare contact coverage than ZoomInfo and Apollo
Emails and mobile numbers come from Dmand AI's healthcare-specific contact sources.How we measure coverageFor an NPI with no contact found
If no current contact exists, the request is marked not found and uses no credits.See pricingWhere NPI data stops
Below, each common source of provider contact data sits beside the Dmand AI API for the same NPI.
Its records exist to identify providers in claims and other transactions, so you get a practice address and an office phone, and still no way to reach the person directly.
A group's site gives you an info@ address or a contact form that the front desk reads first, if anyone does.
Providers change groups and inboxes, and a static file can't re-check an address before you send to it.
The NPPES NPI Registry API has no email field for outreach
From NPIs to contacts
Fieldstone Learning, a CME provider, wants to invite the physicians and nurse practitioners in its CRM to a new course, and it has their NPIs but few of their emails or mobile numbers. The steps follow one request that asks for a professional email and a mobile number for each NPI. Fieldstone Learning and every provider shown are invented.
Illustration: a bulk contact request with three placeholder NPIs that asks for a professional email and a mobile number for each, with a webhook URL, answered with HTTP 202, a batch ID and a request ID for each NPI.
POST https://ext-api.dmand.ai/api/v1/contact/bulkAuthorization: Bearer {{API_KEY}}Content-Type: application/json { "npis": ["{{NPI_1}}", "{{NPI_2}}", "{{NPI_3}}"], "enrich": ["email", "mobile"], "enrichment_email_type": "professional", "webhook": { "url": "https://{{your-server}}/dmand-webhook", "mode": "batch" }, "custom_data": { "campaign": "{{fall-course-invite}}" }}{ "batch_id": "{{batch_id}}", "status": "in-progress", "requests": [ { "npi": "{{NPI_1}}", "request_id": "{{request_id_1}}", "poll_url": "/api/v1/contact/{{request_id_1}}" }, { "npi": "{{NPI_2}}", "request_id": "{{request_id_2}}", "poll_url": "/api/v1/contact/{{request_id_2}}" }, { "npi": "{{NPI_3}}", "request_id": "{{request_id_3}}", "poll_url": "/api/v1/contact/{{request_id_3}}" } ]}01
Fieldstone's developer posts the NPIs to the bulk contact endpoint, asks for a professional email and a mobile number, adds a webhook URL, and gets back HTTP 202 with a batch ID and a request ID for each NPI while Dmand AI looks them up.
02
Only emails validated in the last 30 days come back, so Dmand AI re-checks or looks up anything older, which can take 5 to 10 minutes, and marks a lookup that runs past that as failed. Each NPI shows its status as it goes: accepted, in progress, then completed when at least one contact you asked for is found, or not found.
03
The results arrive as one signed enrich.completed webhook for the batch, or by polling the batch endpoint, with each email and its type, each mobile number, the status and last validation date of each contact, and a found list that shows which contacts came back for each NPI.
04
Credits for every contact you ask for are held when the batch is sent, and each contact is charged only when it is found, 1 for a professional email, 3 for a personal email and 10 for a mobile number; the rest return to the balance, and asking for the same contact for the same NPI again soon after is free.
No developer on hand? The same NPI enrichment runs on a list of providers inside the Dmand AI app.
Dmand AI finds emails for the physicians we need to reach, and the data holds up. The integration was simple, results come back within minutes, and their team has supported us at every step.
NPPES API vs NPI contact API
Most teams use both: the free CMS registry for identity and practice details, and an enrichment API for the provider's own email and mobile number.
Illustration: an NPPES record with a name, NPI type, taxonomy, addresses, office phone and identifiers.
The CMS registry API returns the provider's name, NPI type, taxonomy, practice and mailing addresses, office phone numbers and other identifiers, free and refreshed from NPPES daily.
Illustration: a Dmand AI result with an email, its email type, a mobile number, the last validation date and a status.
It adds the provider's own email and mobile number for the same NPI, with each email labeled professional or personal, the date it was last validated and whether the mailbox is valid or catch-all.
NPI lists by team
Every team starts from NPIs it already holds; what changes is where the NPIs come from and which contact the team needs.
Health IT and services
Send the NPIs stored on contact records in batches and write each verified email back to the same record.
Dmand AI for Health ITHealthtech and digital health
Enrich the NPIs of physicians and nurse practitioners near your programs and invite them to see the product.
Dmand AI for digital healthMedical staffing and recruiting
Ask for personal emails and mobile numbers so a job offer reaches the candidate outside their employer's inbox and front desk.
Dmand AI for staffingConsulting and agencies
Enrich a panel of NPIs by specialty to invite physicians to interviews, advisory calls or surveys for your projects.
Dmand AI for consultingMedTech and medical supplies
Take surgeon NPIs from Medicare procedure data in Dmand AI or your own sources, and add the work email for training and product invites.
Dmand AI for MedTechPharma, biotech and CROs
Send investigator NPIs from your trial site lists and email them about upcoming studies.
Dmand AI for life sciencesTest it on your NPIs
Send NPIs you can check and compare each result with the email your team already uses.
Look up a few providers you know in the app first.
Keys come from the Dmand AI team at hello@dmand.ai.
Use NPIs whose emails your team already has.
Check each email and mobile number, the email type and any not found.
Illustration: a checklist for one batch, with a known email, its type and its validation date checked, and the not-found NPIs still to check.
NPI API questions
What developers and RevOps teams ask before they send their first NPI. Something missing? Email hello@dmand.ai or read docs.dmand.ai.
Yes. The Dmand AI API takes a provider's Type 1 NPI and returns their professional or personal email, validated in the last 30 days, and their mobile number. If no current contact exists, the request is marked not found and uses no credits.
No. The NPPES API from CMS returns registry data such as the provider's name, NPI type, taxonomy, practice and mailing addresses, office phone numbers and other identifiers. Some records list endpoints such as Direct secure messaging addresses, which are for exchanging health information, not for outreach email. To get the provider's own email or mobile number, send the NPI to an enrichment API such as Dmand AI's.
You can ask for an email, a mobile number or both in one request, and for each NPI the API returns a status: completed when at least one contact you asked for is found, not found, or failed. An email comes back with its type (professional or personal), when it was last validated and its email status (valid or catch-all). A mobile number comes back in E.164 format with when it was last validated. Each result lists which contacts were found and the credits it used, and each response shows whether the result was a free repeat and how many credits remain.
Up to 45 NPIs in one bulk request, or one at a time. The default limit is 45 NPIs a minute per API key, and polling counts against it, which is why the docs recommend webhooks. Email hello@dmand.ai to ask for a higher limit.
The API returns only emails validated in the last 30 days. An older email is re-verified, or the NPI is looked up fresh, which can take 5 to 10 minutes. A lookup that doesn't finish in that time is marked failed and its credits are refunded.
It uses the same credits as the Dmand AI app, charged per contact found: 1 credit for a professional email or an email of any type, 3 credits for a personal email and 10 credits for a mobile number. Credits for every contact you ask for are held when you send the request, and any contact that comes back not found, or a lookup that fails, returns its credits to your balance. The same contact for the same NPI requested again within 30 days is free. Plans and credit packs are on the pricing page.
It returns mobile numbers for Type 1 NPIs: add "mobile" to the enrich list of your request, on its own or with "email", and each mobile number found comes back in E.164 format with its last validation date, at 10 credits per mobile number found. That is the provider's own mobile number, not the practice phone listed in the NPI registry. The API doesn't cover executives or people without an NPI yet; for those, use waterfall contact enrichment in the Dmand AI app.
Webhooks are the main delivery method. Add a webhook object with an https URL and choose real-time, one call per NPI, or batch, one call when the whole batch is done. Each call carries an HMAC-SHA256 signature in the X-LNZ-Signature header, and polling the request or batch endpoint works as a fallback.
Type 1 NPIs, the ones CMS assigns to individual providers such as physicians, nurse practitioners and physician assistants. Type 2 NPIs, which belong to organizations such as hospitals and group practices, are not supported.
Provider identity starts from the CMS provider registry (NPPES), the public record behind every NPI. Emails and mobile numbers come from Dmand AI's healthcare-specific contact sources, and each email passes validation before the API returns it, stamped with its last validation date.
API keys are issued by the Dmand AI team, so email hello@dmand.ai to request or rotate one. Send the key as a Bearer token in the Authorization header. The docs at docs.dmand.ai cover authentication, webhooks, credits and rate limits.
The Dmand AI trial is 30 days free, self-serve, no credit card. API keys come from the Dmand AI team, so ask hello@dmand.ai about testing the API, and see the pricing page for which plans include it.
NPI Contact Enrichment
Send your first batch of NPIs and see which providers you can email and call
Send one NPI or a batch, get emails and mobile numbers back by webhook, and pay only for the ones Dmand AI finds.