NPI Healthcare Provider Leads

Healthcare provider prospect lists from the public NPI registry — doctors, practices, specialties and contact details.

Sourced from public registry data. These are business/professional listings for B2B outreach — use them in line with the registry's terms and applicable outreach law.

📊 Sample Output

npi	type	name	primary_specialty	specialties	phone
1912605460	individual	NAWAL AAMIR	Dentist	['Dentist', 'Student in an Organized Health Care Education/Training P…	[phone on record]
1699733048	individual	EUGENE AARON	Dentist, General Practice	['Dentist, General Practice']	[phone on record]
1821228875	individual	KYLE AARON	Dentist	['Dentist']	[phone on record]
1699470385	individual	OMAR AASAR	Dentist, General Practice	['Dentist, General Practice']	[phone on record]
1790307726	individual	SEYEDEH ABAEI	Dentist	['Dentist']	[phone on record]
1184324105	individual	ALPHONSUS ABAH	Dentist, General Practice	['Dentist, General Practice']	[phone on record]

Real rows from run ndrKm5Y3jmBC7guIL on build 0.0.12 (2026-09-24), unedited apart from masked emails/phones and shortened long text; fields the source does not publish are empty.

⚙️ Sample inputs

This is the Store example input — the same input Apify's automated check runs — so it is proven to return rows on the current build. Paste it into the input form, or send it through the API, CLI or a schedule:

{
  "states": [
    "TX"
  ],
  "cities": [],
  "taxonomies": [
    "Dentist"
  ],
  "max_results": 10
}

🔧 Input reference

Field	Type	Default	What it does
states	array	["TX"]	Two-letter state codes (TX, CA...). At least one required - with no state the run returns 0 rows and explains why.
cities	array	[]	Cities to target (e.g. HOUSTON). Provide cities and/or specialties — the NPI registry needs a narrowing field alongside state.
taxonomies	array	["Dentist"]	Provider specialties / taxonomy descriptions (e.g. Dentist, Chiropractor, Physical Therapist, Pharmacy).
enumeration_type	string (both, NPI-1, NPI-2)	"both"	both, NPI-1 (individual providers) or NPI-2 (organizations).
max_results	integer	10	Maximum provider leads to return.
include_raw	boolean	false	Attach the raw NPPES record to each lead.
notionConnector	string		Optional. Connect your Notion workspace and the leads are also written as a Notion page in the same run — the Actor never sees your Notion credentials. Authorize a Notion MCP conn…
notionParentId	string		Optional. The Notion page ID to create the page under. If blank, Notion creates a private page in your workspace.
supabaseConnector	string		Optional. Connect your own Supabase project and the results are also inserted into a table in the same run — the Actor never sees your Supabase credentials. Authorize a write-scop…
supabaseTable	string	"nexgendata_leads"	Target table in the public schema (created if missing, with id, a jsonb data column, and a scraped_at timestamp). Default: nexgendata_leads.
supabaseProjectId	string		Your Supabase project reference (e.g. abcdefghijklmnop). Required unless your connector URL is already project-scoped. Find it in your project URL: supabase.com/dashboard/project/…
deliveryDedup	boolean	true	When on (default), records already delivered in a previous run are not delivered again to the same destination — so scheduled runs only push new items. Turn off to deliver every r…

🧾 JSON sample record

One real record from run ndrKm5Y3jmBC7guIL (emails/phones masked, long text shortened):

{
  "npi": "1912605460",
  "type": "individual",
  "name": "NAWAL AAMIR",
  "credential": null,
  "primary_specialty": "Dentist",
  "specialties": [
    "Dentist",
    "Student in an Organized Health Care Education/Training Program"
  ],
  "phone": "[phone on record]",
  "fax": null,
  "street": "8210 FLOYD CURL DR",
  "city": "SAN ANTONIO",
  "state": "TX",
  "zip": "782293923",
  "mailing_city": "SAN ANTONIO",
  "mailing_state": "TX",
  "status": "A",
  "enumeration_date": "2023-02-22",
  "source_url": "https://npiregistry.cms.hhs.gov/provider-view/1912605460",
  "scraped_at": "2026-09-24T23:58:14.278035+00:00"
}

💰 Pricing

Event	Price (USD)	When it is charged
Actor Start (apify-actor-start)	$0.2	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
Lead returned (apify-default-dataset-item)	$0.1	Charged per lead record returned to the dataset.

Pay-per-event: you pay only for what the run delivers. A run that delivers nothing bills no result events (only the actor-start event, when the actor defines one). Example: a run that delivers 100 results costs 100 × $0.1 = $10.00 plus the start fee.

🔗 Related Actors

More from the NexGenData Healthcare & FDA family:

• FDA Warning Letters & 483 Inspections API
• Medical Device Records — FDA 510(k) & PMA API
• Medicare Provider Records — CMS Doctor Data API

18 more in this family on the NexGenData Store page.

📊 What you get

Clean JSON, one record per lead (full output has 18 fields):

• npi — Npi
• type — Type
• name — Name
• credential — Credential
• primary_specialty — Primary specialty
• specialties — Specialties
• phone — Phone
• fax — Fax
• street — Street
• city — City

Pricing: $0.100 per lead (Pay-Per-Event) — about 10 leads per $1. An Actor Start fee of $0.20 per run also applies (charged per GB of memory, minimum one event). Nothing else is charged: a run that matches no providers returns 0 rows, charges no lead events, and says why in its status message; if the NPI registry is unreachable the run fails instead of finishing green and empty.

🤖 Use with AI agents

Point Claude, the OpenAI Agents SDK, an n8n flow or any MCP-aware client at it and run prospecting on demand.

Agentic payments (x402): Supports agentic payment via x402 — agents can call this actor with USDC, no API key required.

🔗 Related lead-gen actors

Industry lead lists — pick your vertical: Capterra Displacement · Building Permits · DOL Form 5500 · FDIC Banks · Doctor Directory · Restaurants · Auto Dealers · FMCSA Carriers · SBA Recipients · Liquor Licenses · Contractor Licenses · Childcare Licenses

Found your list here? Run it through the chain: verify the emails, enrich the companies, push to your CRM.

The lead-gen workflow chain — found leads? verify → enrich → push to CRM:

1. Find: B2B Leads Finder · Company Email Finder · Person Email Finder · Website Contact Scraper · Yellow Pages
2. Enrich: Company Enrichment · B2B Contact Enricher · Lead List Enricher · Website Tech & Contact Audit
3. Verify & clean: Email Verification · Bulk Email Validator · Lead List Cleaner
4. Deliver: Leads to Notion CRM

Front door — Sales Intelligence MCP: the sales-intelligence agent that fronts this whole cluster → Sales Intelligence MCP

---

Public web & business-source data, assembled as sales-team prospect lists.