NPPES NPI Leads avatar

NPPES NPI Leads

Pricing

$10.00 / 1,000 provider scrapeds

Go to Apify Store
NPPES NPI Leads

NPPES NPI Leads

Scrape public NPPES NPI Registry provider records from the official CMS API for healthcare sales lead generation. Search by state, taxonomy or specialty, and optional city; no login or proxies required.

Pricing

$10.00 / 1,000 provider scrapeds

Rating

0.0

(0)

Developer

Kronos Fox

Kronos Fox

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

NPPES NPI Leads is an Apify actor for collecting public healthcare provider records from the official CMS NPPES NPI Registry API v2.1. It is designed for compliant healthcare sales lead generation, market mapping, territory research, and provider directory enrichment using public data only. The actor does not require logins, cookies, proxies, or private datasets.

Searches are built from the criteria that the NPPES API expects: state plus taxonomy or specialty description, with an optional city filter. Example searches include Nurse Practitioner in Pittsburgh, Dentist in TX, Physical Therapist in FL, or Cardiology in NY. The actor sends a descriptive User-Agent with a contact email, applies a polite delay between requests, and uses request timeouts on every network call.

What you get

Each provider-scraped dataset row is a flattened lead record with the NPI number, provider or organization name, enumeration type, status, credentials, primary taxonomy code and description, all taxonomy descriptions and codes, location address, mailing address, phone and fax fields when available, authorized official details for organizations, the source label, the query that found the record, and a direct CMS provider-view URL.

Healthcare sales lead generation use cases

Use the dataset to build specialty-specific outreach lists, estimate provider density by city or state, enrich CRM records with NPI and taxonomy data, identify organizations in a target care category, or prepare territory plans for healthcare services. Because the source is CMS NPPES, records may include organizations, individuals, mailing addresses, practice locations, and public phone numbers when the registry provides them.

How to run

Provide one or more two-letter states and one or more taxonomy or specialty descriptions. Optionally add city names to narrow each search. Set maxResults to the exact maximum number of provider rows you want. The actor enforces that cap client-side even if the API returns extra rows. The default input is intentionally small and should finish in under five minutes.

Pricing

This actor uses pay-per-event monetization. The single paid event is provider-scraped at $0.01 per provider record pushed to the dataset. Error rows are diagnostic and are not charged as provider records. Local or non-PPE runs are protected by a free cap in the actor code.

FAQ

Is this official CMS data?

The actor reads from the public NPPES NPI Registry API v2.1 hosted by CMS.

Does it scrape private data?

No. It only collects fields returned by the public NPPES API for provider registry records.

Why do I need at least state and specialty?

The NPPES API requires multiple search criteria for broad searches. This actor builds compliant queries from state plus taxonomy or specialty, and optional city.

Can I deduplicate records?

The actor deduplicates NPIs within a run so the same provider is not pushed twice when overlapping city or specialty searches return the same record.