CMS NPI Organization Search - Hospitals Clinics & Providers avatar

CMS NPI Organization Search - Hospitals Clinics & Providers

Pricing

from $2.00 / 1,000 organization results

Go to Apify Store
CMS NPI Organization Search - Hospitals Clinics & Providers

CMS NPI Organization Search - Hospitals Clinics & Providers

Search CMS NPPES for organization (NPI-2) providers — hospitals, clinics, FQHCs, home health, dental practices — by state, city, ZIP, taxonomy, or name. Public API, no key required.

Pricing

from $2.00 / 1,000 organization results

Rating

0.0

(0)

Developer

leo zhu

leo zhu

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Security

Limited permissions

Share

What does CMS NPI Organization Search do?

CMS NPI Organization Search queries the official CMS NPPES NPI Registry API (version 2.1) for organization providers (NPI-2) — hospitals, clinics, FQHCs, home health agencies, dental practices, and other Type 2 NPIs. It is a structured NPPES API / NPI lookup alternative that returns clean JSON to an Apify dataset.

This Actor defaults to organizations only (enumeration_type=NPI-2). It does not scrape individual clinician (NPI-1) profiles, and it never exports authorized official personal names or personal phone numbers.

Why use this Actor?

Use it to build healthcare lead lists, enrich CRM records, monitor facility footprints by city/state/ZIP, or power analytics on hospital and clinic networks — without downloading multi‑GB NPPES flat files.

Features

  • Public CMS API — no API key and no login
  • Organization-only search (NPI-2)
  • Filters: state, city, postal_code, organization_name, taxonomy (preset or custom)
  • Taxonomy presets: Hospital, Home Health, FQHC, Dental
  • Pagination with polite rate limiting (NPPES max ~1,200 records per query)
  • Structured output: NPI, name, status, primary taxonomy, LOCATION address, business phone, dates, NPPES URL
  • Privacy-safe: authorized official PII is omitted
  • Runs on Apify: scheduling, API, webhooks, integrations, monitoring

What data can CMS NPI Organization Search extract?

FieldTypeDescription
npistring10-digit National Provider Identifier
namestringOrganization legal / business name
statusstringNPPES status (e.g. A = Active)
taxonomystringPrimary taxonomy description
taxonomy_codestringPrimary taxonomy code
addressstringPractice LOCATION street address
city / state / postal_codestringLOCATION city, state, ZIP
phonestringOrganization business phone (LOCATION)
enumeration_datestringDate the NPI was enumerated
last_updatedstringLast update date in NPPES
nppes_urlstringLink to the provider in the NPPES registry UI

How to search NPPES organizations

  1. Open the Actor in Apify Console or the Store page.
  2. Set a state (e.g. CA) and a city (e.g. Oakland), or a ZIP / organization name.
  3. Pick a taxonomy preset (Hospital / Home Health / FQHC / Dental) or enter a custom taxonomy description.
  4. Set limit (default 20 for a fast Store auto-test; up to 1200).
  5. Click Start and download results as JSON, CSV, Excel, or HTML.

How much will it cost?

This Actor calls a free public government API. Platform cost is mainly Apify compute. Typical small searches (tens of organizations) finish in seconds on 256–1024 MB. Larger paginated pulls stay under a few minutes. Pay-per-event pricing (if enabled by the publisher) charges per organization result — check the pricing tab on the Store page.

Input

See the Input tab for the full form. Main fields:

  • state — two-letter abbreviation (default CA)
  • city — practice city (default Oakland)
  • postal_code — ZIP / ZIP+4 (wildcards like 946* supported by CMS)
  • taxonomy_preset — Hospital | Home Health | FQHC | Dental
  • taxonomy_description — custom taxonomy text (overrides preset)
  • organization_name — name search with optional trailing *
  • limit — max records (default 20, max 1200)
  • updated_since — optional ISO date; ignored gracefully if the public API has no update filter

Note: NPPES requires more than enumeration_type alone (and more than state alone). Always combine state with city, ZIP, taxonomy, or organization name.

Taxonomy preset mapping

PresetNPPES taxonomy_description
HospitalGeneral Acute Care Hospital
Home HealthHome Health
FQHCFederally Qualified Health Center
DentalDentist

Output

You can download the dataset in JSON, HTML, CSV, or Excel.

Example item:

{
"npi": "1174705362",
"name": "INPATIENT CONSULTANTS OF CALIFORNIA, INC.",
"status": "A",
"taxonomy": "Hospitalist",
"taxonomy_code": "208M00000X",
"address": "350 HAWTHORNE AVE, #2320",
"city": "OAKLAND",
"state": "CA",
"postal_code": "946093108",
"phone": "510-655-4000",
"enumeration_date": "2007-11-29",
"last_updated": "2007-11-29",
"nppes_url": "https://npiregistry.cms.hhs.gov/provider-view/1174705362"
}

Tips

  • Start with a city + taxonomy preset for fast, relevant lists.
  • Raise limit gradually; CMS caps skip at 1000 (about 1200 rows per query shape).
  • For nationwide coverage, run multiple Actor tasks by state or ZIP prefix and merge datasets.
  • Prefer LOCATION address fields already mapped by this Actor when enriching maps or outreach tools.

FAQ & disclaimer

Is an API key required?

No. The NPPES Read API is public.

Does this include individual doctors (NPI-1)?

No. This Actor is scoped to organizations (NPI-2) only.

Are authorized official names exported?

No. Personal authorized-official name and phone fields from NPPES are intentionally omitted.

Source & accuracy

Data comes from CMS NPPES. An NPI does not guarantee that a provider is licensed or credentialed. Always verify critical decisions against primary sources.

Our Actors are ethical and do not extract private user data beyond what CMS publishes in the public NPPES registry for organizations. Personal authorized-official fields are excluded. You should not process personal data unless you have a legitimate reason. If unsure, consult your counsel. GDPR and other privacy laws may apply depending on your use case.

Support

Open an issue on the Actor's Issues tab, or call the Actor via the API tab for programmatic runs and scheduling.